菜单
Investigate GitHub repositories using the gh CLI. Analyze PRs, issues, commits, CI/CD status, repo health, contributor activity, security vulnerabilities, and fetch repo docs/content. Use for any GitHub-related investigation or documentation retrieval.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | github-docs |
| description | Investigate GitHub repositories using the gh CLI. Analyze PRs, issues, commits, CI/CD status, repo health, contributor activity, security vulnerabilities, and fetch repo docs/content. Use for any GitHub-related investigation or documentation retrieval. |
Investigate repositories using gh CLI. All commands assume gh auth status passes.
gh repo view [owner/repo] # Overview, description, stars, forks
gh repo view [owner/repo] --json name,description,defaultBranchRef,stargazerCount,forkCount,issues,pullRequests,url
gh api repos/{owner}/{repo}/readme --jq '.content' | base64 -d # Fetch README
gh api repos/{owner}/{repo}/contents --jq '.[] | "\(.type) \(.name)"' # List root
gh api repos/{owner}/{repo}/contents/{path} # List subdirectory
gh pr list # Open PRs
gh pr list --state all --limit 20 # Recent PRs (any state)
gh pr view <number> # PR details
gh pr view <number> --json title,body,state,author,reviews,comments,commits,files,mergeable,statusCheckRollup
gh pr diff <number> # View diff
gh pr checks <number> # CI status
gh api repos/{owner}/{repo}/pulls/<number>/comments # Review comments
gh api repos/{owner}/{repo}/pulls/<number>/reviews # Reviews with verdicts
gh issue list # Open issues
gh issue list --state all --limit 30 # All recent issues
gh issue list --label "bug" --label "critical" # Filter by labels
gh issue view <number> # Issue details
gh issue view <number> --json title,body,state,author,comments,labels,assignees,milestone
gh api repos/{owner}/{repo}/issues/<number>/timeline # Full issue timeline
gh api repos/{owner}/{repo}/commits --jq '.[0:10] | .[] | "\(.sha[0:7]) \(.commit.author.name): \(.commit.message | split("\n")[0])"'
gh api repos/{owner}/{repo}/commits/<sha> # Single commit details
gh api repos/{owner}/{repo}/compare/base...head # Compare branches/commits
git log --oneline -20 # If in cloned repo
git log --oneline --since="2 weeks ago" # Recent commits
gh run list --limit 10 # Recent workflow runs
gh run view <run-id> # Run details
gh run view <run-id> --log-failed # Failed job logs
gh workflow list # Available workflows
gh api repos/{owner}/{repo}/actions/runs --jq '.workflow_runs[0:5] | .[] | "\(.status) \(.conclusion // "running") - \(.name)"'
gh api repos/{owner}/{repo}/contributors --jq '.[0:10] | .[] | "\(.login): \(.contributions) commits"'
gh api repos/{owner}/{repo}/stats/contributors # Detailed contributor stats
gh api repos/{owner}/{repo}/activity # Recent activity feed
gh api repos/{owner}/{repo}/commits --jq 'group_by(.commit.author.name) | map({author: .[0].commit.author.name, count: length}) | sort_by(-.count)'
gh api repos/{owner}/{repo}/branches --jq '.[].name'
gh api repos/{owner}/{repo}/branches/<branch>/protection # Branch protection rules
gh release list --limit 5 # Recent releases
gh release view <tag> # Release details
gh api repos/{owner}/{repo}/vulnerability-alerts # Dependabot alerts (requires admin)
gh api repos/{owner}/{repo}/secret-scanning/alerts # Secret scanning alerts
gh api repos/{owner}/{repo}/code-scanning/alerts # Code scanning alerts
gh api repos/{owner}/{repo}/dependabot/alerts --jq '.[] | "\(.security_advisory.severity): \(.security_advisory.summary)"'
gh search repos "keyword" --limit 10 # Search repos
gh search repos "keyword" --owner {org} # Search within org
gh search issues "error" --repo owner/repo # Search issues in repo
gh search prs "fix" --repo owner/repo --state merged # Search merged PRs
gh search code "function_name" --repo owner/repo # Search code
gh pr view <n> --json title,body,author,state,commits,files,reviews,statusCheckRollupgh pr diff <n> - examine changesgh pr checks <n> - CI statusgh api repos/{o}/{r}/pulls/<n>/reviews - review verdictsgh api repos/{o}/{r}/pulls/<n>/comments - inline commentsgh issue list --state open --limit 50 --json number,title,labels,createdAt,authorgh issue view <n> for details on high-priority itemsgh api repos/{o}/{r}/issues/<n>/timeline for full contextgh repo view --json stargazerCount,forkCount,issues,pullRequests,updatedAtgh pr list --state open - PR backloggh issue list --state open - Issue backloggh run list --limit 5 - CI healthgh api repos/{o}/{r}/contributors - active maintainersgh release list --limit 3 - release cadencegh run list --limit 5 - find failed rungh run view <id> - which job failedgh run view <id> --log-failed - error logsgh run rerun <id> - retry if flakyMost commands support --json for structured output:
gh pr list --json number,title,author,createdAt --jq '.[] | "\(.number): \(.title) by \(.author.login)"'
API endpoints paginate. Use --paginate or iterate:
gh api repos/{o}/{r}/issues --paginate --jq '.[].title'
Always specify repo when not in a clone:
gh pr list --repo owner/repo
gh issue view 123 --repo owner/repo
Automatically fix security vulnerabilities by updating affected dependencies. Triggered by the "vuln:" command followed by space-separated tokens. Each token is either JIRA-ID:VULN-ID (e.g. MGD-2423:CVE-2023-46604) or a bare VULN-ID (e.g. CVE-2023-46604) when no Jira ticket exists. Handles CVE IDs automatically by looking them up on NVD. Skips CWE and OWASP IDs with a warning. For each CVE: fetches the affected library, checks if it is used in the repo, finds the minimal safe version, runs baseline tests, applies the fix, rebuilds, re-runs tests, then commits to a new branch and opens a pull request. Use when the user wants to remediate one or more security vulnerabilities in the current repository.
Upgrade one or more components (libraries, frameworks, languages, build tools, CI/CD actions) in the current repository to a target version. Triggered by the "upgrade:" command followed by space-separated tokens in the form "component:version", "component:minor", "component:latest", "component:lts", or bare "component" (latest compatible assumed). Works on any project regardless of language or ecosystem. Upgrades are applied to the current branch with no commits or PRs. Runs tests before and after each upgrade; updates test code if required by the new version. Use when the user wants to keep dependencies, frameworks, languages, or CI/CD actions current.
Use Atlassian CLI (acli) to manage Jira Cloud work items: authenticate, search/fetch tickets by project and status, update/edit fields, transition status, assign, comment, and perform safe bulk operations with JQL. Trigger this skill when the user asks to list Jira tickets, change status, edit issues, or automate Jira workflows via acli.