AugmentClaude

PR Description

Generate well-formatted pull request titles, bodies, and comments.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/pr-description-jgravelle/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

The PR title and body template, and the rules for any comment drafted for a reporter or contributor. Load when writing a PR body, a release PR, or a triage response.

What this skill does

PR description and comment drafts

Authority: CLAUDE.md "Output Rules" and "Sentence shapes that read as machine-written"; "Issue + release policy" 1, 2, 3a, 3b; the spokesperson agent for anything outward-bound.

PR title

<type>: <what changed, one line> with (#N) when it closes an issue; release: vX.Y.Z - <thesis> for a release PR.

PR body, in this order, headings as written

  1. What was wrong (or missing): two to four sentences, the reporter credited by login.
  2. Why: the mechanism, and whether it is a regression of a Standing lesson or an ARCHAEOLOGY row (name it).
  3. What is now impossible (or possible): the property, not the instance; the other spellings checked.
  4. Evidence: paste verbatim, never retype: bench_table.md, surface.md, surface_descriptions.md, the review verdict line.
  5. Definition of Done: checklist.md verbatim.
  6. Closes #N when applicable.

No number appears in 1-3 that is not in 4 or 5.

Comment drafts (triage, close comments)

  • One issue, one verdict; propose the split, do not merge findings.
  • A timebox states the deadline AND the default in the same sentence, never longer than 24 hours, and never advertises an extension clause.
  • Name the version the fix ships in; 43% of closes did not.
  • Never answer a concrete pain with aggregate statistics.
  • The draft goes through spokesperson; posting is the next layer's.

Related skills