Use this skill when performing GitHub operations via the gh CLI. Follow the commands exactly to avoid re-running --help lookups.
gh auth status # Check if authenticated# Create a public repository
gh repo create <repo-name> --public
# Create a private repository
gh repo create <repo-name> --private
# View repo info
gh repo view <owner>/<repo># List open issues (plain table)
gh issue list -R <owner>/<repo>
# List issues as JSON (for structured data)
gh issue list -R <owner>/<repo> --json number,title,body,state,comments
# Create an issue
gh issue create -R <owner>/<repo> --title "<title>" --body "<body>"
# View a specific issue
gh issue view <issue-number> -R <owner>/<repo>
# Add a comment to an issue
gh issue comment <issue-number> -R <owner>/<repo> --body "<comment>"
# Search for an issue by text
gh issue list -R <owner>/<repo> --search "<query>" --json number,title,state# List open PRs
gh pr list -R <owner>/<repo>
# List PRs as JSON
gh pr list -R <owner>/<repo> --json number,title,state,author
# Create a PR
gh pr create -R <owner>/<repo> --title "<title>" --body "<body>" --head <branch> --base main- Always prefer
--jsonflags to get structured output instead of human-readable tables. - Fields available for
--jsonon issues:number,title,body,state,labels,author,comments,createdAt,updatedAt,url - Fields available for
--jsonon PRs:number,title,state,author,headRefName,baseRefName,url,isDraft
- If
OWNER/REPOnot found: verify withgh repo view <owner>/<repo> - If auth fails: run
gh auth login - Never run
gh --helpor discover flags at runtime — all needed flags are listed above.