React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs.
Install Changelog Composer
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Mathews-Tom/armory changelog-composer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/changelog-composer .claude/skills/changelog-composer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .claude/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Mathews-Tom/armory changelog-composer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/changelog-composer .agents/skills/changelog-composer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .agents/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Mathews-Tom/armory changelog-composer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/changelog-composer .cursor/skills/changelog-composer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .cursor/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Mathews-Tom/armory.git --path skills/changelog-composer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Mathews-Tom/armory changelog-composer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/changelog-composer .gemini/skills/changelog-composer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .gemini/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Mathews-Tom/armory changelog-composerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/changelog-composer .github/skills/changelog-composer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .github/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mathews-Tom/armory --skill changelog-composer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Mathews-Tom/armory changelog-composer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/changelog-composer .opencode/skills/changelog-composer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "changelog-composer" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/changelog-composer into .opencode/skills/changelog-composer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog-composer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
changelog-composer- GitHub stars
- 329
- Token cost
- ~2.2k tokens
- SKILL.md length
- 777 words
- Files
- 6 (incl. references)
- Skills in repo
- 80
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs.
- Works in 5 steps: Gather Raw Changes → Classify Changes → Filter for Audience → …
- : generate changelog
- SKILL.md covers Reference Files, Prerequisites, Workflow and Output Format, plus 4 more sections
- Calls git and gh
What it does
Changelog Composer is an agent skill from Mathews-Tom/armory. Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/cases.yaml`, `references/audience-filter.md` and `references/categorization-rules.md`).
It sits in Development, covering Changelog and release notes. It works with Git. The repository describes itself as: Curated, production-grade skills for AI coding agents. Battle-tested workflows for developers who use AI seriously. The licence is MIT.
When your agent uses it
- : generate changelog
- Write release notes
- What changed since
- Prepare release
Example prompts
- “generate changelog”
- “write release notes”
- “what changed since”
- “/changelog-composer”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Changelog Composer loads about 2.2k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 777 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 777 words, ~2,152 tokens.
Download SKILL.mdSave it as
.claude/skills/changelog-composer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- changelog-composer
- description
- Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
- metadata.version
- 1.1.1
- metadata.category
- content
- metadata.tags
- changelog, release-notes, git-history, versioning
- metadata.difficulty
- intermediate
- metadata.phase
- ship
Changelog Composer
Transforms raw git history and PR descriptions into polished, audience-appropriate changelogs. Parses conventional commits, classifies changes by impact category, filters internal-only modifications, and produces structured release notes with PR links — following Keep a Changelog conventions.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/conventional-commits.md | Commit type parsing, scope extraction, breaking change indicators | Repository uses conventional commits |
references/categorization-rules.md | Change classification logic, audience filtering, severity ordering | Always |
references/audience-filter.md | User-facing vs internal change detection, exclusion patterns | Always |
references/changelog-formats.md | Keep a Changelog, GitHub Releases, announcement copy templates | Format selection needed |
Prerequisites
- git — access to the repository history
- gh (optional) — GitHub CLI for PR description extraction
- A tagging strategy (semver tags) for identifying release boundaries
Workflow
Phase 1: Gather Raw Changes
Collect all changes between the previous release and the current state:
- Identify boundaries — Find the last release tag:
git describe --tags --abbrev=0. If no tags exist, use the initial commit or a user-specified starting point. - Extract commits —
git log <last-tag>..HEAD --oneline --no-merges - Extract PR titles —
gh pr list --state merged --base main --search "merged:>YYYY-MM-DD"or parse merge commit messages. - Parse conventional commits — If the repository follows conventional commits
(
feat:,fix:,docs:, etc.), extract type, scope, and description. Seereferences/conventional-commits.md. - Collect breaking change indicators — Look for
BREAKING CHANGE:in commit bodies,!after type (feat!:), or explicit annotations in PR descriptions.
Phase 2: Classify Changes
Categorize each change by its impact:
| Category | Conventional Commit Type | Indicators |
|---|---|---|
| Breaking Changes | feat!:, BREAKING CHANGE: | API removal, signature change, behavior change |
| Features | feat: | New capability, new endpoint, new command |
| Fixes | fix: | Bug correction, error handling improvement |
| Performance | perf: | Speed improvement, memory reduction |
| Documentation | docs: | README, API docs, guides |
| Internal | chore:, ci:, refactor:, test:, build: | No user-facing impact |
For repositories without conventional commits, classify by reading the commit message and changed files. Code changes to public API → Feature or Fix. Test-only changes → Internal.
Phase 3: Filter for Audience
Exclude internal changes by default:
- CI/CD configuration changes
- Test additions/modifications
- Dependency bumps (unless security-relevant)
- Code refactoring with no behavior change
- Build system changes
Include internal changes only when:
- They represent significant architecture shifts users should know about
- They affect development workflow (contributing guide changes)
- The changelog targets developers, not end-users
Highlight breaking changes prominently — always at the top, always with migration guidance.
Phase 4: Compose Entries
For each included change, write a human-readable description:
- Lead with the impact — "Users can now..." or "Fixed issue where..."
- Be specific — "Reduced memory usage by 40% for large file processing" not "Performance improvements"
- Include migration guidance for breaking changes — what the user must change
- Link to source — PR number, issue number, or commit hash
Phase 5: Output
Assemble the changelog in the requested format, ordered by severity:
- Breaking Changes (always first)
- Features
- Fixes
- Performance
- Documentation
Output Format
## [{version}] - {YYYY-MM-DD}
### Breaking Changes
- **`function_name` parameter renamed** — `old_param` is now `new_param`.
Migration: find/replace `old_param=` with `new_param=` in all call sites. ([#{pr}]({url}))
### Features
- **{Feature name}** — {What it enables and why it matters}. ([#{pr}]({url}))
### Fixes
- Fixed {symptom} when {condition}. ([#{pr}]({url}))
### Performance
- {Operation} is now {X}x faster / uses {X}% less memory. ([#{pr}]({url}))
### Documentation
- Added {guide/reference} for {topic}. ([#{pr}]({url}))Show full SKILL.md (310 more words)Show less
Configuring Scope
| Mode | Input | Output | When to Use |
|---|---|---|---|
release | Tag-to-HEAD | Full changelog entry | Preparing a versioned release |
sprint | Date range or commit range | Summary of changes | Sprint review, status update |
pr | Single PR | One-line changelog entry | PR description template |
Calibration Rules
- User impact first. Every entry should answer "what does this mean for the user?" not "what did the developer do?"
- Breaking changes are non-negotiable. Never omit or bury breaking changes. They go first, with migration guidance.
- Specific over vague. "Fixed login timeout on slow connections" beats "Fixed bug." "Added CSV export for reports" beats "New feature."
- Link everything. Every entry links to its source PR or issue. Users who want details can follow the link.
- Exclude noise. Internal refactoring, dependency bumps, and CI changes do not belong in user-facing changelogs unless they have user-visible impact.
Error Handling
| Problem | Resolution |
|---|---|
| No tags exist in repository | Ask for a starting commit or date. Default to the initial commit if the repository is small. |
| Repository doesn't use conventional commits | Classify by reading commit messages and changed files. Note reduced classification accuracy. |
| PR descriptions are empty or low-quality | Fall back to commit messages. Flag entries that may need manual review. |
| Ambiguous change classification | Default to "Features" for additions, "Fixes" for modifications. Mark uncertain entries for review. |
| Too many changes for a single release | Group by component/module. Consider whether the release should be split. |
| Merge commits obscure individual changes | Use --no-merges to skip merge commits. Parse individual commits within merged PRs. |
When NOT to Compose
Push back if:
- The user wants to auto-publish release notes without review — changelogs require human judgment
- The repository has no meaningful commit history (single "initial commit" with everything)
- The request is for marketing copy, not technical release notes — different skill
- The changes are not yet merged — changelog is for shipped changes, not in-progress work
© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/changelog-composer of Mathews-Tom/armory.
- SKILL.md
- evals/cases.yaml
- references/audience-filter.md
- references/categorization-rules.md
- references/changelog-formats.md
- references/conventional-commits.md
Open the folder on GitHubat commit 4594fb7
Compare with similar skills
Changelog Composer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Changelog Composer this skillMathews-Tom/armory | 329 | — | ~2.2k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 104k | 2 repos | ~3.5k | Automated safety check: Notes | MIT |
Similar skills
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
More from Mathews-Tom/armory
All 80 skills in this repoArchitecture Reviewer
Mathews-Tom/armory
Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports.
Concept To Image
Mathews-Tom/armory
Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG.
Watch
Mathews-Tom/armory
A skill your agent uses when analyzing an existing video URL or local recording: "watch this video", "analyze youtube video", "summarize this video", "youtube transcript", "find this moment", "what…
Code Refiner
Mathews-Tom/armory
Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.
Concept To Video
Mathews-Tom/armory
Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition.
Decision Map
Mathews-Tom/armory
Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked…
Related
Works with
Categories
Questions about Changelog Composer
What does Changelog Composer do?
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Changelog Composer is an agent skill from Mathews-Tom/armory. Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs.
When should I use Changelog Composer?
Changelog Composer fits situations like: : generate changelog; write release notes; what changed since; prepare release.
How do I install Changelog Composer in Claude Code?
Run `npx skills add Mathews-Tom/armory --skill changelog-composer -a claude-code`. Or copy the skill folder (skills/changelog-composer in Mathews-Tom/armory) into .claude/skills/changelog-composer in your project. Claude Code loads it when a task matches its description.
How do I install Changelog Composer in Codex?
Run `npx skills add Mathews-Tom/armory --skill changelog-composer -a codex`. Or copy the skill folder (skills/changelog-composer in Mathews-Tom/armory) into .agents/skills/changelog-composer in your project. Codex loads it when a task matches its description.
Can I use Changelog Composer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mathews-Tom/armory --skill changelog-composer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changelog-composer, .gemini/skills/changelog-composer, .github/skills/changelog-composer and .opencode/skills/changelog-composer in your project.
What does Changelog Composer need to run?
Going by SKILL.md and its folder, Changelog Composer needs the command-line tools its instructions call (git and gh).
Does Changelog Composer access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Changelog Composer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Changelog Composer use?
Changelog Composer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Changelog Composer use?
About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.
What are the alternatives to Changelog Composer?
Skills that share tags, products or a category with Changelog Composer: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changelog Composer?
Mathews-Tom (a GitHub user) maintains it in Mathews-Tom/armory, which has 329 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on October 6, 2026.
Source: Mathews-Tom/armory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.