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/gen-release-notes.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/gen-release-notes)<a href="https://agentmods.dev/commands/existential-birds/amelia/gen-release-notes"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/gen-release-notes/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/gen-release-notes"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/gen-release-notes.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.00009 | $0.02338 |
| Opus 5.5 | $0.00004 | $0.00935 |
| Sonnet 5.5 | $0.00002 | $0.00468 |
| Haiku 4.5 | $0.00001 | $0.00234 |
Grade A, and why
gen-release-notes 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate professional release notes following the Keep a Changelog standard.
Input: Previous tag (e.g., v0.0.1)
$ARGUMENTS
Use extended thinking to analyze the changes thoroughly before generating release notes.
Step 1: Gather Changes
Run these commands to collect information about changes since the provided tag:
# Store the previous tag
PREV_TAG="$ARGUMENTS"
# Verify the tag exists
git tag -l "$PREV_TAG"
# Get the repo URL for PR links
git remote get-url origin
# List commits since last tag
git log ${PREV_TAG}..HEAD --pretty=format:"%h %s" --no-merges
# Get detailed diff stats
git diff ${PREV_TAG}..HEAD --stat
# List changed files by directory
git diff ${PREV_TAG}..HEAD --name-only | sort | uniq
Also gather PR information:
# Get merged PRs since the tag (requires gh CLI)
gh pr list --state merged --search "merged:>=$(git log -1 --format=%ci $PREV_TAG | cut -d' ' -f1)" --json number,title,author,labels
Step 2: Analyze and Categorize
Categorize each change into exactly one of these groups (in this order):
| Category | Include | Exclude |
|---|---|---|
| Added | New features, new public APIs, new CLI commands | Internal utilities not exposed to users |
| Changed | Modified behavior, performance improvements, updated dependencies with user impact | Refactors with no behavior change |
| Deprecated | Features marked for future removal | - |
| Removed | Deleted features, removed public APIs | Removed internal code |
| Fixed | Bug fixes, error handling improvements | Test-only fixes |
| Security | Vulnerability patches, security hardening | - |
Exclude entirely:
- CI/CD configuration changes (unless they affect users)
- Documentation-only changes (unless they reveal new features)
- Code style/formatting changes
- Test-only changes
- Internal refactors with no user-visible impact
- Merge commits
Step 3: Determine Version Number
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 · 287 lines · 9 tokens per session scan A ca690e0d3966
gen-release-notes is a command published in the GitHub repository existential-birds/amelia (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 2,338 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
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
sweep-mode-c-lifecycle
If Mode C was selected, the wave lifecycle is the back half of the issue-side lifecycle: no Curator, no Approval gate, no Builder. Each PR is routed by its current label to Judge, Doctor→Judge, or Merge directly.
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.
post-release.en
Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.
release-tag
Create and push a version tag after a release PR has been merged.