菜单
Manage GitHub repositories — create and review pull requests, check CI/actions status, search code, manage issues, and approve or merge changes. Use this skill for any GitHub project workflow including code review, releases, and hotfixes, even if the user doesn't explicitly say GitHub or PR.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/shanehull/dotfiles --skill github命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Fetch climate and ENSO data from NOAA Climate Prediction Center — Niño SST anomaly indices (weekly/monthly), Oceanic Niño Index (ONI), Southern Oscillation Index (SOI), and ENSO diagnostic advisory text. Use this skill when the user asks about El Niño, La Niña, ENSO status, Pacific sea surface temperatures, Southern Oscillation, or climate patterns affecting weather, agriculture, or commodity markets, even if they don't name ENSO, NOAA, or CPC explicitly.
Create detailed business overviews for investment research — deep-dive through business model, management, financials, valuation, risks and tracking. Use this skill only when the user explicitly asks to do a business overview, deep dive, or formal company write-up.
Fetch stock data and financial information — quotes, price history, company financials, option chains, market sectors, institutional holders, insider transactions, news, and screeners. Use this skill when the user asks about stocks, company financials, options, market analysis, or stock screening, even if they don't mention a ticker symbol or Yahoo Finance.
基于 SOC 职业分类
正在显示 SKILL.md
| name | github |
| description | Manage GitHub repositories — create and review pull requests, check CI/actions status, search code, manage issues, and approve or merge changes. Use this skill for any GitHub project workflow including code review, releases, and hotfixes, even if the user doesn't explicitly say GitHub or PR. |
| compatibility | Requires `gh` CLI. |
| allowed-tools | Bash(git:*), Bash(gh:*), Bash(cat:*), Read |
Single surface: gh CLI for read + write (lifecycle, comments, CI watching, search).
git status first; ask the user before adding.gh user (no flag changes this).@me = current user. Branch names work wherever a PR number does.-R owner/repo.--json <fields> (requires explicit field list, e.g. --json number,title,state)..github/PULL_REQUEST_TEMPLATE.md when using --fill or no body flag.Auth: gh auth status to check. gh auth login --hostname github.com to log in (pick HTTPS + browser).
# Create
gh pr create --fill --assignee @me
gh pr create --fill --assignee @me --reviewer user --label foo --draft
# With repo template
template=$(cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null)
gh pr create --title "..." --body "$template" --assignee @me
# View / comment
gh pr view [123|branch] --comments
gh pr view --web
gh pr comment [123] --body "comment"
# List
gh pr list --assignee @me
gh pr list --search "reviewer:@me label:needs-review draft:true"
# Lifecycle
gh pr review 123 --approve [-R owner/repo]
gh pr review 123 --request-changes --body "..."
gh pr merge 123 --squash --delete-branch
gh pr close 123
gh pr ready 123
gh pr edit 123 --add-reviewer user
# Diffs / commits / checks
gh pr diff 123
gh pr checks 123 [--watch]
# Issues
gh issue create --title "..." --body "..." --assignee @me --label bug
gh issue list --assignee @me
gh issue view 123 --comments
gh issue comment 123 --body "comment"
gh issue close 123
# CI / Actions
gh run list [--workflow=ci.yml]
gh run view <run-id> [--log-failed]
gh run watch <run-id>
gh workflow run <workflow> -f key=value
# Search
gh search prs "is:open author:@me"
gh search issues "is:open label:bug"
gh search code "func Foo" --owner owner --repo repo
# Find usernames
grep -i "name" .github/CODEOWNERS
Draft → ready: gh pr create --fill --draft --assignee @me → gh pr checks --watch → gh pr ready + gh pr edit --add-reviewer user.
Hotfix: gh pr create --fill --assignee @me --reviewer lead --label hotfix → gh pr checks --watch → gh pr merge --squash --delete-branch.
Review: gh pr list --search "review-requested:@me" → gh pr view 123 --comments → gh pr review 123 --approve.
Conventional Commits: Use Conventional Commits for all commit messages and PR titles.
Simple branch names: Use feat/, fix/, docs/, ci/, or chore/ prefixes followed by a short slug (e.g. feat/oauth-retry). No ticket IDs, team names, or usernames.
Never commit to main: Always branch, commit, push, and create a PR. The only exception is gh pr merge. No direct pushes to main or master.
Concise PR descriptions: Lead with the purpose of the change, then add only what a reviewer needs — links to related PRs/issues, code snippets highlighting key points, before/after notes. Skip checklists unless they track work inside this PR.