agentmods.dev

pr-description

A workflow for writing a pull request description from the changes on the current Git branch. A pull request is a request to review and merge code into another branch.

In plain words
What is it for?
Use it to prepare a review summary, explain how to test the changes, answer the repository's template questions, or update an existing pull request after approval.
Why use it?
It gathers the relevant diff, commits, base branch, template, and testing details so the description does not have to be assembled from memory.

Command for Claude Code

1.3k 1mo ago A scan 0 tokens original MIT
View the source file storybookjs/react-native
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/storybookjs/react-native/pr-description
Clone the repo
git clone --depth 1 https://github.com/storybookjs/react-native

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 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.00000 $0.00352
Opus 5 $0.00000 $0.00176
Sonnet 5 $0.00000 $0.00070
Haiku 4.5 $0.00000 $0.00035

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

Security

Grade A, and why

pr-description 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-description.md · 39 lines

What it actually says

Generate PR Description

Generate a pull request description based on the changes in the current branch.

Instructions

  1. First, determine the base branch by checking for a PR or using next as default:

    gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null || echo "next"

  2. Analyze the changes in this branch compared to the base branch:

    • Run git diff <base>..HEAD --stat to see changed files
    • Run git diff <base>..HEAD to see the actual changes
    • Run git log <base>..HEAD --oneline to see commit messages

  3. Read the PR template at .github/PULL_REQUEST_TEMPLATE.md

  4. Generate a PR description following the template structure:

    • Issue: Link related issues or write "N/A" with context
    • What I did: Summarize the changes with bullet points for specific modifications
    • How to test: Provide clear steps to verify the changes work
    • Answer the template questions about examples and documentation

  5. Check if a PR exists for this branch:

    gh pr view --json number 2>/dev/null

  6. If a PR exists, ask the user if they want to update it with the generated description using gh pr edit.

Guidelines

  • Be specific about version changes (e.g., "1.0.0 → 2.0.0")
  • Highlight breaking changes prominently
  • Group related changes together
  • Keep the description concise but informative
  • Use code blocks for commands in "How to test"
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 · 39 lines · 0 tokens per session scan A 62b58f56514c

Subscribe to this mod's changes

pr-description is a command published in the GitHub repository storybookjs/react-native (1,311 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 352 tokens. 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.

Code reviewGit and workflowReActTestingexporeact-nativestorybook
Related

Other commands, from other repositories

create-bucket-docs

Create documentation for a Lingo.dev bucket type using analysis output.

lingodotdev/lingo.dev · 12 tokens

analyze-bucket-type

Analyze a bucket type implementation to identify all behaviors and configurations.

lingodotdev/lingo.dev · 11 tokens

gaia-release

Cut a new GAIA release, bump version, graduate CHANGELOG, regenerate manifest, open release PR, then tag on merge. Maintainer-only.

gaia-react/gaia · 34 tokens

speckit-gaia-wiki-promote

Promote merged SPEC or plan content into the GAIA wiki.

gaia-react/gaia · 23 tokens

health-audit

Maintainer-only autonomous health audit + auto-heal loop. Runs N=3 fresh-team audit-fix-audit cycles with circuit breakers, reports an F-to-A+ verdict (folding in the shared Claude-integration fitness grade) or escalates.

gaia-react/gaia · 55 tokens

speckit-gaia-plan-close

Close a plan after implementation+merge. Offers wiki-promote for the plan's consolidated SUMMARY.md, cold-consolidates an out-of-band merge, then early-reaps the local plan folder once cost is represented in cost.jsonl.

gaia-react/gaia · 55 tokens