updating-changelog
Analyze PR changes to automatically generate and update migration notes and changelog documentation.
Install
mkdir -p .claude/skills/updating-changelog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3602" && unzip -o skill.zip -d .claude/skills/updating-changelog && rm skill.zipInstalls to .claude/skills/updating-changelog
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Updates changelog documentation for contract developers and node operators by analyzing branch changes relative to 'next'. Use when preparing a PR, updating migration notes, documenting breaking changes, or when asked to update changelog/release notes.Key capabilities
- →Analyze git diffs between development branches
- →Categorize changes into breaking, features, and deprecations
- →Draft release notes and migration entries
- →Format documentation for contract developers and node operators
How it works
The skill compares the current branch against the next branch to identify code changes, then formats these findings into specific markdown files following established project conventions.
Inputs & outputs
When to use updating-changelog
- →Draft release notes for a new PR
- →Update migration notes for contract changes
- →Document breaking API changes
- →Create changelog entries for node operators
About updating-changelog
This skill analyzes `git` diffs between development branches to identify features, breaking changes, and deprecations. It then formats these changes into appropriate changelog or migration markdown files.
Updates changelog documentation for contract developers and node operators by analyzing branch changes relative to 'next'. Use when preparing a PR, updating migration notes, documenting breaking changes, or when asked to update changelog/release notes.
When not to use it
- →When changes are not relative to the next branch
Prerequisites
Limitations
- →Requires manual review of draft entries before file updates
- →Dependent on consistent use of component tags
How it compares
It automates the categorization and formatting of release notes based on project-specific documentation standards rather than manual drafting.
Compared to similar skills
updating-changelog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| updating-changelog (this skill) | 1 | 7mo | Review | Intermediate |
| releasenotes | 1 | 3mo | No flags | Beginner |
| bd-to-br-migration | 1 | 8mo | Review | Intermediate |
| readme-sync | 0 | 3mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AztecProtocol
View all by AztecProtocol →You might also like
releasenotes
exceptionless
Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.
bd-to-br-migration
Dicklesworthstone
Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
readme-sync
hiroshi0530
|
pr-demo
mikeyobrien
Use when creating animated demos (GIFs) for pull requests or documentation. Covers terminal recording with asciinema and conversion to GIF/SVG for GitHub embedding.
tutorial-any-repo
TKONIY
Automatically generate a file-by-file code tutorial website for any repository. Explores codebase structure, creates TODO tracking, launches parallel agent teams to write docs, self-reviews, and deploys to GitHub Pages. Use when user says "write a tutorial for this project", "explain this codebase",
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.