菜单
Use when working with GitHub from the command line, especially repositories, issues, pull requests, reviews, Actions, projects, releases, API calls, or GitHub-specific automation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when building, redesigning, or polishing frontend screens, UI components, web apps, dashboards, landing pages, games, or interactive tools where visual quality, interaction feel, responsive layout, or product fit matters.
Use when writing, reviewing, pruning, or refactoring tests and there is risk of low-value tests, implementation-detail assertions, over-mocking, redundant coverage, brittle setup, or tests that do not protect a real public contract.
Use when the user explicitly asks for deep research / 深度研究 / 深入调研, or when they need evidence-driven, multi-source research for a decision, report, due diligence, current-state analysis, technical comparison, recommendation, or contested/high-stakes question.
Use when the user asks for a non-fiction book summary, 高保真读书笔记, 拆书, 导读, argument map, chapter study guide, application manual, reading route, critical evaluation, multi-book synthesis, or interactive book-learning dialogue.
Use when rewriting, editing, or drafting prose so it sounds specific, situated, and human rather than generic, over-polished, or AI-like. Works for Chinese and English prose, messages, essays, fiction, dialogue, memoir-like writing, public copy, and explanatory text. Focuses on voice, reader effort, scene logic, uneven human rhythm, and concrete context. Avoids template tone, consultant phrasing, fake warmth, excessive symmetry, moral summaries, and detector-gaming.
Find evidence-backed architecture deepening opportunities in a codebase. Use when the user wants to improve architecture, find refactoring opportunities, consolidate shallow or tightly-coupled modules, improve testability, or make a repository easier for AI agents to navigate.
| name | gh-cli |
| description | Use when working with GitHub from the command line, especially repositories, issues, pull requests, reviews, Actions, projects, releases, API calls, or GitHub-specific automation. |
Use this as a chaptered reference. Read the smallest chapter that matches the task, then apply the conventions chapters for body formatting and review policy.
| Topic | Read first |
|---|---|
| Setup, auth, CLI shape | Quick Start |
| Repository operations | Repositories |
| Issues | Issues |
| Pull requests | Pull Requests |
| Review policy and inline replies | Review Policy |
| Cross-command body rules | Conventions |
| Actions / workflow automation | Actions |
| Projects | Projects |
| Releases, gists, codespaces, org, search, labels, keys | Platform Surfaces |
| API, rulesets, attestations, preview, agent tasks, output formats | API and Ops |
| Common workflows, environment, best practices | Workflows and Best Practices |
gh <command> --help or the official manual.--body-file - or --raw-field body="$(cat <<'EOF' ... EOF)" for multiline bodies.\n in quoted body strings.P0-P3, render the level with a Shields badge.Use gh help <topic> and the official GitHub CLI manual when a command is rare enough that the chapter does not cover it.