// Use GitHub CLI (gh) for common operations like creating PRs, viewing GitHub Actions logs, managing issues, reviewing PRs, and more. When merging PRs via gh, prefer rebase merge over squash or merge commits unless repo policy or the user explicitly requests otherwise.
Break unstaged or mixed changes into small, atomic, logical git commits with Conventional Commit messages. Use when the user asks to commit, stage, or split changes — e.g. 'help me commit', 'commit my changes', 'break these into logical commits', 'what should I commit first', 'stage my changes', 'commit atomically', or 'make atomic commits'. Uses git diff, git add -p, and Conventional Commits (feat:/fix:/refactor:/chore:/docs:/test:/style:/perf:/build:/ci).
Break long-lived pull request branches into a mergeable stack of small PRs with clear dependency order and story flow. Use when a branch has grown too large, when the user asks to split a PR into stacked PRs, or when each PR must be reviewable in about 5 minutes while preserving logical narrative across the stack.
Improve coherence in drafts by diagnosing broken flow, rewriting transitions, aligning paragraph purpose, and preserving author voice. Use when a user says things like 'make this coherent', 'tighten the flow', 'this feels choppy', 'can you smooth transitions', or asks to revise prose in Markdown, notes, essays, blog posts, emails, or docs so ideas connect cleanly from sentence to sentence and section to section.
Use Slack CLI (`slack`) for app lifecycle and workspace operations including login/logout, create/init, run/deploy, manifest validation, trigger management, app install/uninstall, environment management, and diagnostics. Use when users ask to run or troubleshoot commands like `slack create`, `slack run`, `slack deploy`, `slack trigger`, `slack manifest`, `slack auth`, `slack activity`, `slack datastore`, `slack env`, or request help-first progressive discovery with `slack help` and `slack SUBCOMMAND --help`, plus version/documentation alignment and stale-skill refresh.
Use the MemPalace CLI to persist, search, and manage AI memory across sessions. Triggers whenever the user asks to remember, recall, save, store, or retrieve information that should persist across conversations — including past decisions, preferences, facts about people or projects, conversation history, and any verbatim content the user wants preserved. Also triggers when the user mentions "palace", "wings", "rooms", "drawers", "knowledge graph", "AAAK", or when they want to search through historical context, traverse connections between topics, or check what their AI knows. Mirrors the MemPalace MCP server tools: each CLI command maps to an MCP tool with an equivalent trigger condition.
Guide for design-driven development with prescribed folder structure. New features use full workflow (HLD → LLD → EARS). Bug fixes skip doc creation but verify intent coherence.
| name | gh-cli |
| description | Use GitHub CLI (gh) for common operations like creating PRs, viewing GitHub Actions logs, managing issues, reviewing PRs, and more. When merging PRs via gh, prefer rebase merge over squash or merge commits unless repo policy or the user explicitly requests otherwise. |
| license | MIT |
This skill provides quick access to common GitHub CLI operations for managing repositories, pull requests, issues, and GitHub Actions.
gh (GitHub CLI) - must be authenticated with your GitHub accountgh auth login if not already authenticatedWhen merging with gh pr merge, prefer rebase merge (--rebase): it reapplies the PR commits on top of the base branch for a linear history. Do not default to squash (--squash) or a merge commit (--merge / plain merge) unless the user or repo policy explicitly asks for that style.
Create a new PR:
gh pr create --title "Your PR title" --body "Description of changes"
Create a PR with auto-fill (from commit messages):
gh pr create --fill
Create a draft PR:
gh pr create --draft --title "WIP: Feature X"
List PRs:
# List open PRs
gh pr list
# List all PRs (including closed)
gh pr list --state all
# List your PRs
gh pr list --author @me
View a PR:
# View PR in terminal
gh pr view 123
# Open PR in browser
gh pr view 123 --web
Check out a PR locally:
gh pr checkout 123
Review a PR:
# Approve
gh pr review 123 --approve
# Request changes
gh pr review 123 --request-changes --body "Please fix the typo"
# Comment
gh pr review 123 --comment --body "Looks good overall"
Merge a PR (default to rebase; see Merge policy):
# Preferred: rebase and merge (linear history)
gh pr merge 123 --rebase
# Auto-merge when checks pass (still use rebase)
gh pr merge 123 --auto --rebase
# Only when explicitly desired: merge commit
gh pr merge 123 --merge
# Only when explicitly desired: squash and merge
gh pr merge 123 --squash
List workflow runs:
# List recent runs
gh run list
# List runs for a specific workflow
gh run list --workflow "CI"
# List failed runs
gh run list --status failure
View run details:
gh run view 1234567890
View run logs:
# View all logs for a run
gh run view 1234567890 --log
# View logs for a specific job
gh run view 1234567890 --log --job "build"
Download run logs:
gh run download 1234567890
Re-run a workflow:
# Re-run failed jobs
gh run rerun 1234567890 --failed
# Re-run all jobs
gh run rerun 1234567890
Watch a running workflow:
gh run watch 1234567890
Trigger a workflow manually:
gh workflow run workflow-name.yml
Create an issue:
gh issue create --title "Bug: Something broken" --body "Description here"
List issues:
# List open issues
gh issue list
# List your issues
gh issue list --assignee @me
# List issues with a label
gh issue list --label bug
View an issue:
gh issue view 456
Comment on an issue:
gh issue comment 456 --body "Thanks for reporting this!"
Close/reopen an issue:
gh issue close 456
gh issue reopen 456
Clone a repository:
gh repo clone owner/repo
Create a repository:
# Create public repo
gh repo create my-repo --public
# Create private repo with README
gh repo create my-repo --private --add-readme
View repository info:
gh repo view owner/repo
Fork a repository:
gh repo fork owner/repo --clone
Set default branch:
gh repo set-default owner/repo
Check CI status:
# View checks for current branch
gh pr checks
# View checks for a specific PR
gh pr checks 123
View your notifications:
gh notify
Use with specific repository:
gh pr list --repo owner/repo
Output as JSON for scripting:
gh pr list --json number,title,author,state
Use custom queries:
# Search for PRs with label
gh pr list --label "needs-review"
# Search for issues assigned to you
gh issue list --assignee @me --state open
Check command help: Add --help to any command to see all options:
gh pr create --help
Interactive mode: Many commands support interactive prompts when you don't provide required flags:
gh pr create # Will prompt for title, body, etc.
Aliases: Create custom aliases for frequently used commands:
gh alias set prc 'pr create --fill'
Default repository: Run gh repo set-default in a repo to avoid specifying --repo flag.
Creating a PR from current branch:
git push -u origin feature-branch
gh pr create --fill
Checking why a PR failed:
gh pr checks 123
gh run view <run-id> --log
Quick PR review workflow:
gh pr list
gh pr view 123
gh pr checkout 123
# Make local tests/review
gh pr review 123 --approve
Monitoring a deployment:
gh run list --workflow "Deploy"
gh run watch <latest-run-id>