Borrowing it
Nothing to install: this file belongs to yuji0809/cc-recommender. 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/yuji0809/cc-recommender/main/.claude/commands/pr-description-en.mdgit clone --depth 1 https://github.com/yuji0809/cc-recommenderWrote 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/yuji0809/cc-recommender/pr-description-en)<a href="https://agentmods.dev/commands/yuji0809/cc-recommender/pr-description-en"><img src="https://agentmods.dev/badge/commands/yuji0809/cc-recommender/pr-description-en/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/yuji0809/cc-recommender/pr-description-en"><img src="https://agentmods.dev/badge/commands/yuji0809/cc-recommender/pr-description-en.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.00016 | $0.00881 |
| Opus 5.5 | $0.00006 | $0.00352 |
| Sonnet 5.5 | $0.00003 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
pr-description-en 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are tasked with generating a comprehensive Pull Request description in English for the current branch.
Steps to Execute
1. Determine Base Branch
Run these commands to detect the base branch:
BASE_BRANCH=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name 2>/dev/null || echo "main")
echo "Base branch: ${BASE_BRANCH}"
2. Analyze Changes
Gather commit history and file changes:
# Get commit messages
git log ${BASE_BRANCH}..HEAD --pretty=format:"%s"
# Get changed files with status
git diff ${BASE_BRANCH}...HEAD --name-status
# Get file statistics
git diff ${BASE_BRANCH}...HEAD --stat
3. Determine Change Types
Analyze commits and files to determine the type of changes:
- 🐛 Bug fix: Commits starting with
fix: - ✨ New feature: Commits starting with
feat:or new files insrc/ - 💥 Breaking change: Commits with
BREAKING CHANGEorfeat!:,fix!: - 📝 Documentation update: Commits starting with
docs:or only*.mdchanges - 🎨 Code style update: Commits starting with
style: - ♻️ Refactoring: Commits starting with
refactor: - ⚡ Performance improvement: Commits starting with
perf: - ✅ Test update: Commits starting with
test:or only*.test.tschanges
4. Check for Existing PR
gh pr view --json url,title,state 2>/dev/null
If a PR exists, ask the user if they want to update it or just view the generated description.
5. Generate PR Description
Create a comprehensive PR description in English following the template at .github/PULL_REQUEST_TEMPLATE.md:
Structure:
- Description: Summarize all changes from commit messages
- Changed Files: List new and modified files with brief explanations
- Motivation and Context: Explain why these changes are needed
- Type of Change: Check all applicable boxes based on analysis
- How Has This Been Tested: Indicate test commands run
- Checklist: Mark completed items
- Additional Notes: Include implementation approach, future enhancements, breaking changes (if any)
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.
- 1mo ago First seen · 120 lines · 16 tokens per session scan A 5cf28ee830b8
pr-description-en is a command published in the GitHub repository yuji0809/cc-recommender (10 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 881 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
create-pr
Run PR checks, push to remote, create PR, and generate description automatically.
generate-pr-desc
Generate and update PR description from branch commits using GitHub CLI.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
nyann:doctor
Run nyann's read-only hygiene + documentation audit on the current repo. Emits the same drift sections retrofit uses, but never offers remediation or writes to the filesystem. Use this on session start, in CI, or any time you want to sanity-check a repo without risking mutations.
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
nyann:hotfix
Create the branch topology for a patch release against a previously tagged version. Ensures release/ . exists from the source tag, then creates hotfix/ off it. After this, the user commits the fix and runs /nyann:release from the hotfix branch.