Pr describer

Skill nanoodlecom/noodle-skills/skills/pr-describer

Ready-to-install agent skills, each wrapping a nanoodle visual AI workflow — poster, photo restyle, jingle, narrated poem, video teaser

Install

npx -y skills add nanoodlecom/noodle-skills --skill pr-describer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.9 KB, as published. Nobody here has run it

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 >= 20 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

Key	Required	What to pass
`Diff`	yes	The unified diff, usually `@/tmp/pr-diff.txt`
`Drafter`	no	Override the drafter's house style (that node's system prompt)
`Auditor`	no	Override the auditor's instructions (that node's system prompt)
`Final PR body`	no	Override 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.

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagein 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

run the nanoodle pr-describe workflow
write the branch diff to a text file first
prefer an existing ambient NANOGPT_API_KEY
never print the API key
pipe the output directly into a new pull request
mention the cost before batch-processing pull requests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.