Borrowing it
Nothing to install: this file belongs to istarwyh/mcpadvisor. 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/istarwyh/mcpadvisor/main/.claude/commands/generate-changelog.mdgit clone --depth 1 https://github.com/istarwyh/mcpadvisorWrote 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/istarwyh/mcpadvisor/generate-changelog)<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/generate-changelog"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/generate-changelog/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/istarwyh/mcpadvisor/generate-changelog"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/generate-changelog.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.04158 |
| Opus 5.5 | $0.00000 | $0.01663 |
| Sonnet 5.5 | $0.00000 | $0.00832 |
| Haiku 4.5 | $0.00000 | $0.00416 |
Grade A, and why
generate-changelog 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate CHANGELOG.md from git commit history: $ARGUMENTS.
This command supports multiple modes:
- Full changelog: Generate changelog from all commits since last tag
- PR changelog: Generate changelog for the latest merged PR only
- Range changelog: Generate changelog for specific commit range
USAGE MODES
Mode 1: Latest PR Changelog
claude generate-changelog --pr
claude generate-changelog --latest-pr
Mode 2: Full Version Changelog
claude generate-changelog
claude generate-changelog --full
Mode 3: Custom Range Changelog
claude generate-changelog --range v1.0.0..HEAD
claude generate-changelog --since v1.0.0
PLAN
- Determine changelog scope (PR, full, or range)
- Analyze commit history and identify relevant commits
- Parse conventional commits to categorize changes
- Generate structured changelog with proper formatting
- Update existing CHANGELOG.md or create new one
- Validate and commit the changelog updates
PREREQUISITES
-
Ensure you're on the main branch with latest changes:
git checkout main git pull origin main -
Verify git history is available:
git log --oneline -10
CHANGELOG GENERATION
Step 1: Determine Scope and Get Commits
Use TodoWrite tool to track progress, then determine which commits to include:
For Latest PR Mode (--pr or --latest-pr):
# Find the most recent merged PR
LATEST_PR=$(gh pr list --state merged --limit 1 --json number --jq '.[0].number')
echo "Latest merged PR: #$LATEST_PR"
# Get PR details
gh pr view $LATEST_PR --json title,headRefName,baseRefName,mergeCommit
# Get commit range for the PR (from merge base to merge commit)
MERGE_COMMIT=$(gh pr view $LATEST_PR --json mergeCommit --jq '.mergeCommit.oid')
BASE_BRANCH=$(gh pr view $LATEST_PR --json baseRefName --jq '.baseRefName')
PR_BRANCH=$(gh pr view $LATEST_PR --json headRefName --jq '.headRefName')
# Find merge base and get PR commits
MERGE_BASE=$(git merge-base origin/$BASE_BRANCH $MERGE_COMMIT)
COMMIT_RANGE="$MERGE_BASE..$MERGE_COMMIT"
echo "PR commit range: $COMMIT_RANGE"
echo "Commits in PR #$LATEST_PR:"
git log $COMMIT_RANGE --oneline --pretty=format:"%h %s"
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 · 478 lines · 0 tokens per session scan A 0f61e3d2b55e
generate-changelog is a command published in the GitHub repository istarwyh/mcpadvisor (89 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,158 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.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.