メニュー
Write or amend the title or description of an existing PR. Use whenever updating PR prose, including after pushing new commits to a branch with an open PR.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ai2cm/ace --skill write-pr-proseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | write-pr-prose |
| description | Write or amend the title or description of an existing PR. Use whenever updating PR prose, including after pushing new commits to a branch with an open PR. |
| model | claude-opus-4-6[1m] |
| context | fork |
You are writing the title and/or description for a PR: the one for the current checked-out branch, or one the user names. PR titles and descriptions in this repository are authored through this skill so that the model pinned in its frontmatter writes them; context: fork scopes the pin to exactly this work (a bare model: pin is turn-scoped and would leak into the rest of the turn or lapse on the next prompt). The pinned model is a deliberate choice (Jeremy, 2026-08-20) — do not bump it without user permission.
Once you've updated the PR prose, leave a comment on the PR which states you have done so and which model you are actually running, so a silent fallback to the session model (e.g. if the pinned model is ever retired) stays visible. Note in the same comment any context the helper script below failed to retrieve (its (warning: ...) lines), so gaps in what informed the prose are visible too.
.claude/skills/write-pr-prose/gather_pr_context.sh [<pr-number>] (defaults to the current branch's PR). It prints the existing title and description, the PR discussion (issue comments, reviews, and inline review comments), and the full diff from the PR's base branch — so a stacked PR is described against its own base, not main. The script requires an existing PR; if it exits with an error (no PR found, or the diff could not be retrieved), stop and report the failure instead of writing prose. Read all of it: the existing prose and the comments often carry intent the diff alone does not, and the title and description must reflect the whole change from the PR's base per the guidance in AGENTS.md, not just the recent commits..github/pull_request_template.md. Keep the template's checklist lines rather than deleting them: tick only items actually done, and leave inapplicable items unchecked with a brief in-place reason.gh pr edit <number>.