pr-desc

A command that writes a commit message or pull-request description from the changes in the current Git repository. It follows the repository's conventional-commit style, a format that labels changes such as fixes, features, and documentation.

In plain words
What is it for?
Use it when preparing a commit or pull request to produce a title, summary, reason for the change, and test plan without committing anything.
Why use it?
It saves time summarising a change while keeping the wording consistent with the project's existing history and avoiding unsupported references to hooks or tools.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/childrentime/reactuse/pr-desc
Clone the repo
git clone --depth 1 https://github.com/childrentime/reactuse

Made for: Claude Code.

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00164
Opus 5 $0.00010 $0.00082
Sonnet 5 $0.00004 $0.00033
Haiku 4.5 $0.00002 $0.00016

Measured yesterday against content hash dbc102673432, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pr-desc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/pr-desc.md · 15 lines

What it actually says

Generate a PR/commit description for the current change. Use the pr-description skill.

  1. Read the real change: git diff (or git diff origin/main...HEAD on a branch), git diff --stat, and git log --oneline -10 to match the prevailing style.
  2. Produce a type(scope): summary title and a tight body (What / Why / Test plan, plus an optional AI-assistance note).
  3. Verify any hook references against scripts/hook-registry.json — never invent a name or URL.

Output the description in a code block ready to paste. Don't commit.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 15 lines · 21 tokens per session scan A dbc102673432

Subscribe to this mod's changes

pr-desc is a command published in the GitHub repository childrentime/reactuse (1,047 stars, last pushed 11d ago), licensed Unlicense. It adds 21 tokens to every session and 164 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.