Command	Description
`gh issue list`	List open issues in current repo
`gh issue list --repo <owner/repo>`	List issues in a specific repo
`gh issue view <number>`	View issue details
`gh issue create --title "..." --body "..."`	Create an issue
`gh issue close <number>`	Close an issue
`gh issue comment <number> --body "..."`	Comment on an issue
`gh issue edit <number> --assignee "@me"`	Assign to yourself

Command	Description
`gh pr list`	List open PRs
`gh pr view <number>`	View PR details and diff
`gh pr create --title "..." --body "..."`	Create a PR
`gh pr merge <number> --squash`	Merge a PR (squash)
`gh pr review <number> --approve`	Approve a PR
`gh pr review <number> --request-changes --body "..."`	Request changes
`gh pr comment <number> --body "..."`	Comment on a PR
`gh pr checks <number>`	Show CI check status for a PR

gh api repos/<owner>/<repo>/issues      # List issues via API
gh api graphql -f query='...'           # GraphQL queries

Usage Examples

Create a bug report issue:

gh issue create \
  --title "Fix: null pointer in auth flow" \
  --body "Steps to reproduce: ..." \
  --label "bug" \
  --assignee "@me"

Check CI status for latest PR:

gh pr list --limit 1
gh pr checks <number>

Review a PR and request changes:

gh pr view 42
gh pr review 42 --request-changes --body "Please add tests for the edge case on line 87."

Trigger a manual workflow dispatch:

gh workflow run deploy.yml --field environment=staging

Rules

Always check if CLI is installed and authenticated: gh auth status
If not installed, show brew install gh && gh auth login and stop
If not authenticated, show gh auth login and stop
Default to the current repo (detected from git remote) unless user specifies <owner/repo>
When listing issues/PRs, show number, title, author, and date — limit to 10 by default
When viewing PR diffs, truncate at 100 lines and save full diff to workspace/pr-<number>.diff
NEVER approve or merge a PR without the user explicitly confirming
For code review, summarize the diff first, then provide specific line-level feedback
Keep responses concise: action confirmation in 1-2 lines, details in collapsible sections when possible