agentleFS
nanoodlecomnanoodlecom/noodle-skills/skills/pr-describer/SKILL.md

pr-describer

Skill2 starsChanged 22 days agoMITView on GitHub

Turn a git diff into a self-audited PR description — one LLM drafts the body, a second audits the draft against the raw diff for missed breaking changes and unmentioned files, a third folds the findings in. Use when opening a pull request and the description should mention everything the diff actually changes.

  • Reads credentials
  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never print the key.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PR describer

Runs the bundled nanoodle workflow workflows/pr-describe.noodle-graph.json against the NanoGPT API — a three-stage text pipeline over one input (Diff): a drafter writes a conventional PR body (summary, ## Changes, ## Test plan), an auditor compares the draft against the raw diff and lists every breaking change, behavioral shift, or touched file the draft omits, and a reviser emits the final markdown (Final PR body) with every audit finding folded in (adding ## Breaking changes when needed). Requires Node.js 22.23.4+, 24.22.1+, or 26.12.1+ and the nanoodle npm package (npx nanoodle fetches it).

API key

The run needs a NanoGPT API key. Use whichever is available:

  • NANOGPT_API_KEY already set in the environment — prefer this; no extra flags.
  • A .env file containing NANOGPT_API_KEY=... — pass --env-file <path> only when the key is not already in the environment. (With this CLI, --env-file overrides ambient NANOGPT_API_KEY.)

Never print the key.

Run

From this skill's directory (or prefix paths if running from elsewhere). Write the branch diff to a .txt file first (@path reads .txt/.md files as text):

npx nanoodle run workflows/pr-describe.noodle-graph.json \
  --input "Diff=@/tmp/pr-diff.txt"

Producing the diff file is the usual one-liner, e.g. git diff origin/main...HEAD > /tmp/pr-diff.txt.

The output is text, so no --out directory is needed. Pipe the body straight into GitHub:

npx nanoodle run workflows/pr-describe.noodle-graph.json --input "Diff=@/tmp/pr-diff.txt" \
  | jq -r '.outputs["Final PR body"]' | gh pr create --title "..." --body-file -

Inspect the interface anytime with:

npx nanoodle inspect workflows/pr-describe.noodle-graph.json

Inputs

KeyRequiredWhat to pass
DiffyesThe unified diff, usually @/tmp/pr-diff.txt
DrafternoOverride the drafter's house style (that node's system prompt)
AuditornoOverride the auditor's instructions (that node's system prompt)
Final PR bodynoOverride the reviser's instructions (that node's system prompt)

Each optional key is a node name from the editor, and it replaces that node's system prompt. Final PR body is the reviser node's name, so it is both an optional input key and the output key. A rename cannot separate them — it renames both. The two halves never meet: the input sets the reviser's system prompt, the output carries the reviser's result, and neither is ambiguous, because each namespace holds one Final PR body.

--input "Final PR body=<custom reviser instructions>"   # sets the reviser's system prompt
--input "Drafter=<custom house style>"                  # sets the drafter's system prompt
--input "Auditor=<custom audit instructions>"           # sets the auditor's system prompt

outputs["Final PR body"] still carries the finished description.

Outputs

  • Final PR body is a text output: printed on the Final PR body: stderr line and included in the stdout JSON as outputs["Final PR body"] — the finished markdown PR description.

Serve as an MCP tool

The same graph file works unchanged as a typed MCP tool with one required string input:

mkdir -p ~/noodles && cp workflows/pr-describe.noodle-graph.json ~/noodles/pr-scribe.json
claude mcp add nanoodle -- npx nanoodle-mcp --graphs ~/noodles

Cost

Each run costs about $0.01 in NanoGPT credit (three zai-org/glm-5.2 calls; scales with diff size). Pure text, pennies per call — but runs spend real credit, so mention cost before batch-processing a backlog of PRs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.