菜单
Use this skill when the user shares a GitHub URL (issue or pull request). Automatically fetch details using GitHub CLI (gh command). Triggered by URLs like github.com/himkt/.claude/issues/123 or github.com/himkt/.claude/pull/123. Do NOT run gh commands directly — always invoke this skill first.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Format responses for non-native English speakers by using simplified English and adding a Japanese explanation of the original message. Use when the user invokes /bilingual-explain, or asks for easy English with Japanese notes. Applies to the current response and all subsequent responses in the session until the user cancels it.
Review the user's English writing and produce structured feedback with a fluency score, passage-level revisions, and sophistication suggestions that go beyond simple grammar fixes. Use when the user invokes /english-review, asks to review or polish their English, or asks for feedback on chat messages, commit messages, or prose they have written. This is also the canonical format used by the Stop-hook English reviewer.
Systematic investigation of NixOS boot failures (crash after reboot, kernel panic, black screen after update, system won't boot). Guides through journal log analysis, generation comparison, and fix proposal. Use when a user reports their NixOS system fails to boot or crashes after reboot but works with nixos-rebuild switch.
Explain the implementation of a symbol by tracing its definition using LSP. Use when user asks to explain, trace, or understand how a specific symbol (function, class, variable) is implemented. Takes symbol name as argument. Do NOT rely on grep and reading files alone — use this skill for accurate LSP-based tracing.
| name | github-cli |
| description | Use this skill when the user shares a GitHub URL (issue or pull request). Automatically fetch details using GitHub CLI (gh command). Triggered by URLs like github.com/himkt/.claude/issues/123 or github.com/himkt/.claude/pull/123. Do NOT run gh commands directly — always invoke this skill first. |
Fetch GitHub issues and pull requests with gh + --json + --jq.
{owner}, {repo}, {number} from the URL. If only a number was given, run gh repo view --json nameWithOwner -q .nameWithOwner.--jq to project fields and, when relevant, drop out-of-scope rows. Unfiltered comment/review/file payloads run to thousands of lines; a focused filter shrinks input 10–100×.Use gh --jq directly — do not pipe to external jq. The local Bash validator rejects multi-command pipes.
Common select(...) predicates:
select((.created_at | fromdateiso8601) > (now - 10800))select(.user.login == "...")select(.state == "OPEN")select(.in_reply_to_id == null)# Issue
gh issue view {url} --json title,author,body,state,labels,comments --jq '...'
# PR overview
gh pr view {url} --json title,author,body,state,reviewDecision,baseRefName,headRefName,comments --jq '...'
# Diff (do NOT use gh api for diffs)
gh pr diff {url} # full
gh pr diff {url} --name-only # files only
# Inline review comments
gh api repos/{owner}/{repo}/pulls/{number}/comments --paginate --jq '[.[] | {user: .user.login, path, line, body, html_url, created_at}]'
# Review summaries
gh api repos/{owner}/{repo}/pulls/{number}/reviews --paginate --jq '[.[] | {user: .user.login, state, body, submitted_at}]'
# CI checks
gh pr checks {url}
gh pr create --fill # auto-populate title+body from commits
gh pr edit {number} --add-reviewer @copilot # always request Copilot review immediately after
Use --title / --body-file only when the user explicitly asks for a custom title/body.