菜单
Generate a PR title and description from the committed diff against the default branch. Use when the user asks to draft, write, or prepare a pull request description/body. Does not create the PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Respond to unreplied review comments on the current GitHub Pull Request. For each comment, either commit a fix, push, and reply with the commit hash, or reply with concrete rationale for keeping the code as-is. Does not approve or request changes.
日本語の技術文書・書籍原稿の文章規範。整形（一文一行、引用ブロック、脚注、コラム記法）、段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。
Non-Antigravity agents only. Get an independent second opinion from Antigravity CLI (agy). agy cannot be driven headlessly from a sandboxed agent Bash, so this skill hands the user a ready-to-run command and folds in their pasted reply.
Methodology for iteratively improving agent-facing instructions (skills / slash commands / CLAUDE.md / code-gen prompts) via bias-free executor + two-sided evaluation (self-report + instruction-side metrics). Meta-skill, invoke ONLY when the user explicitly asks for an "empirical" eval of a prompt or skill, or for the Iter-0 description / body consistency check. Do NOT auto-invoke after every skill edit; this loop is operator-triggered by name.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Draft a commit message from staged changes. Matches the style of recent commits in the repo, emphasizes why over what, and does not run `git commit`.
| name | github-pull-request-describe |
| description | Generate a PR title and description from the committed diff against the default branch. Use when the user asks to draft, write, or prepare a pull request description/body. Does not create the PR. |
Generate a PR title and description from the diff against the default branch.
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@', fallback main)git fetch origin, then git log --oneline origin/<default>..HEAD and git diff origin/<default>...HEAD- #123), or the single line N/A when there are none.$ARGUMENTS is provided, use it as additional context.Boundary rule for Why vs What: "why is this work needed" belongs in Why; "what was decided, among which alternatives, and why that choice" belongs in What.
Do NOT create the PR. Write the draft to /tmp/pr-description.md as the canonical artifact — chat rendering can introduce trailing whitespace invisibly, so the file (not the chat output) is the source of truth. Verify cleanliness and copy to the clipboard:
grep -nE '[[:blank:]]+$' /tmp/pr-description.md && echo "FAIL: trailing whitespace" || pbcopy < /tmp/pr-description.md
Also show the same content in a single fenced code block for in-chat preview (any fence style — triple backticks or tildes — works; the template below uses ~~~). Do not leave trailing whitespace on any line.
<title>
## Why
<motivation — 1-3 sentences>
## What
<design approach and reasoning — prose or bullets, not a diff summary>
## References
- <issue/PR>
When there are no references, replace the bullet under ## References with a single bare line N/A (do NOT write - N/A).