Borrowing it
Nothing to install: this file belongs to existential-birds/amelia. 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/existential-birds/amelia/main/.claude/commands/amelia/update-pr-desc.mdgit clone --depth 1 https://github.com/existential-birds/ameliaWrote 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/existential-birds/amelia/update-pr-desc)<a href="https://agentmods.dev/commands/existential-birds/amelia/update-pr-desc"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/update-pr-desc/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/existential-birds/amelia/update-pr-desc"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/update-pr-desc.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.00008 | $0.00888 |
| Opus 5.5 | $0.00003 | $0.00355 |
| Sonnet 5.5 | $0.00002 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
update-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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Pull Request Description
Update an existing PR description when additional fixes or changes have been made after the original PR was opened.
Use Cases
- Follow-up fixes after code review feedback
- Additional changes discovered during testing
- Expanding scope based on new requirements
- Bug fixes found during PR review
Instructions
1. Find the Current PR
# Get the PR number for current branch
gh pr view --json number,title,body,url,createdAt
# Get the original PR description
gh pr view --json body --jq '.body'
# Get the base commit (when PR was created)
gh pr view --json baseRefName,headRefName,commits
2. Analyze New Changes
# Get the original PR merge base
MERGE_BASE=$(git merge-base main HEAD)
# Find commits added since PR was opened
# (Compare against the first commit in the PR)
FIRST_COMMIT=$(gh pr view --json commits --jq '.commits[0].oid')
# Show new commits (those after the first PR commit)
git log --oneline ${FIRST_COMMIT}..HEAD
# Show what files changed in new commits
git diff --stat ${FIRST_COMMIT}..HEAD
# Get detailed view of new changes
git diff ${FIRST_COMMIT}..HEAD
3. Prepare Updated Description
Preserve the original PR content and append a "Follow-up Changes" section:
<original PR body preserved as-is>
---
## Follow-up Changes
<Date or context for when these changes were added>
### Additional Changes
- <Change 1: what and why>
- <Change 2: what and why>
### New Commits
- `<sha>` <commit message>
- `<sha>` <commit message>
### Reason for Changes
<Brief explanation of why follow-up changes were needed>
- Code review feedback
- Bug discovered during testing
- Expanded scope
- etc.
4. Update the PR
gh pr edit --body "$(cat <<'EOF'
<complete updated body here>
EOF
)"
5. Add a Comment (Optional)
For visibility, add a PR comment summarizing the update:
gh pr comment --body "$(cat <<'EOF'
## PR Updated
Added follow-up changes:
- <brief summary of changes>
See updated PR description for details.
EOF
)"
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 · 171 lines · 8 tokens per session scan A 51dfd1f47344
update-pr-desc is a command published in the GitHub repository existential-birds/amelia (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 888 once invoked, about $0.0000 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-30.
Other commands, from other repositories
settle-threads
The previous round read unresolved review threads on the pull request, and this round's implementer judged each one like a review finding: fixed it, declined it with evidence, or found it needs a decision this run cannot make. Decide which threads are settled and write the reply each one gets. You write nothing…
code-review
Review the current branch changes for bugs and style issues.
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.
end
End a work session - a settlement pass that reconciles uncommitted / unpushed work + session context into git, the tracker, and a session snapshot file. --session (aliases --snapshot, --pre-compact, --compact) skips settlement and only writes the shared snapshot, keeping the session going.
Hexagonal.Gatekeeper
Your role is to perform a deep, architecture-focused code review on a specific branch. You must validate that all changes strictly follow Hexagonal Architecture (Ports & Adapters) principles and align with the existing codebase patterns.
Code.Review
Your task is to perform a deep, non-superficial code review on the target branch.