Use this skill whenever the prompt contains any `github.com` URL, even if the user only pastes a link and gives no GitHub-specific keywords.
Handles git and GitHub operations using the gh CLI.
Triggers include any GitHub link to an issue, pull request, commit, compare page, Actions run, release, discussion, or repository.
Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology with git log/blame/bisect.
Also in this package
Other skills from mcollina/skills · top by installs.
Interactive rebasing for clean history (commit splitting, squashing)
Cherry-pick, bisect, worktrees
Advanced merge strategies
Submodule and subtree management
Git hooks setup and maintenance
Repository archaeology with git log/blame/show
GitHub operations via gh CLI:
Create/manage PRs with proper templates
Open PRs with explicit base/head and clear concise content, e.g. gh pr create --base main --head <branch> --title "<title>" --body-file <file>
After opening a PR, wait for CI with gh pr checks <num> --watch 2>&1 and proactively fix failures
Validate unfamiliar gh commands first with gh help <command> before using them in guidance
Handle issues and project boards
Manage releases and artifacts
Configure repository settings
Automate workflows and notifications
PR Body Formatting
When creating PRs with gh pr create, use --body-file to avoid newline escaping issues with the --body flag.
PR descriptions should stay simple:
Write a short description of the change in plain prose
Do not add subsections or headings such as ## Summary or ## Testing
Do not include a testing section
Architecture changes may need a slightly longer description if extra context is necessary
cat > /tmp/pr-body.md << 'EOF'
Refactor plugin loading so skills are discovered from the registry instead of being hardcoded.
EOF
gh pr create --body-file /tmp/pr-body.md
Using a temporary file is cleaner, more reliable, and easier to debug.
Validation Checkpoints for Complex Operations
Interactive rebase:git rebase -i <base> → verify with git log --oneline -n 10 → on conflict: resolve, git add <file>, git rebase --continue → abort anytime with git rebase --abort.
Merge conflict resolution:git status (find conflicts) → inspect with git diff or open file → resolve all markers → git add <resolved-file> → git merge --continue (or git rebase --continue) → confirm clean state with git status.
