Borrowing it
Nothing to install: this file belongs to nimble-giant/ailloy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nimble-giant/ailloy/main/.claude/commands/pr-description.mdgit clone --depth 1 https://github.com/nimble-giant/ailloyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/nimble-giant/ailloy/pr-description)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/pr-description"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nimble-giant/ailloy/pr-description"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00455 |
| Opus 5.5 | $0.00000 | $0.00182 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 2mo ago.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-description
Generate a pull request description for the current branch changes.
Usage
claude pr-description
Title
The title of the pr should adhere to our git conventional commit guidelines to make our titles consistent.
Description
This command generates a comprehensive PR description by comparing the current branch to the head of main using git diff main.... The PR description is saved as a markdown file in the /pr-descriptions folder.
If the /gh-issue command was used and Claude knows what GitHub issue the branch is for, the PR description should begin with closes #<github-issue-number>.
Output
- Location:
/pr-descriptionsfolder - File naming:
pr-description-YYYY-MM-DD-HH-MM-SS.mdor descriptive name based on feature - Format: Markdown with clear section headers
Required Sections
Summary
Brief description of the PR purpose (1-3 sentences)
Changes
List of specific changes made (bullet points)
UAT
Instructions for how to test the changes
Example Structure
# feat(web): add control families to compliance section
closes #1234
## Summary
This PR adds support for Control Families in the Judge web UI, allowing users to organize compliance controls into logical groupings. Control families create a hierarchy between frameworks and controls.
## Changes
- Added Control Families menu item in Compliance section
- Created new page and components for viewing/managing control families
- Added family column to Controls table
- Updated GraphQL queries to include control family information
- Added hooks for querying, creating, and updating control families
## UAT
1. Navigate to Compliance > Families
2. Create a new control family
3. Create a control and assign it to the family
4. Verify the control shows up in the family's detail page
Notes
- Only generate when explicitly requested with
claude pr-description,/pr-description, or when directly asked to "create a PR description" - Always compare current branch to main branch for complete context
- Do not include Claude Code attribution or generated-by notices in PR descriptions
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.
- 2mo ago First seen · 70 lines · 0 tokens per session scan A fbb7f9549f98
pr-description is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 455 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-31.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.