write-changelog
This skill updates project changelogs by focusing on user-facing benefits rather than technical implementation details.
Install
mkdir -p .claude/skills/write-changelog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7865" && unzip -o skill.zip -d .claude/skills/write-changelog && rm skill.zipInstalls to .claude/skills/write-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.
Write or update changelog entries with user-focused languageKey capabilities
- →Categorize entries into features, bug fixes, changes, or internal updates
- →Maintain an unreleased section for new entries
- →Format entries to emphasize user benefits
- →Standardize release note language
How it works
The skill enforces a specific markdown structure and tone, requiring entries to be placed in the unreleased section of the changelog file.
Inputs & outputs
When to use write-changelog
- →Adding a new feature to the changelog
- →Documenting bug fixes for users
- →Updating changelogs with release notes
- →Maintaining versioned release history
About this skill
Changelog
Write or update changelog entries following these guidelines:
Guidelines
- Focus on user benefits rather than implementation details
- Keep entries concise - typically a single line without subpoints
- Emphasize what the user can now do or how their experience improves
- Avoid technical specifics like state management, CSS classes, or internal architecture
Categories
Entries are organized under these category headings:
### ✨ Features- New functionality for users### 🐛 Bug Fixes- Corrections to existing behavior### 🔁 Changes- Modifications to existing features### ⚙ Internal- Technical changes (use sparingly, still user-focused)### 🌐 Translations- New or updated translations### Breaking changes- For major releases only### Deprecated- Features being phased out
Unreleased Section
Always add new entries to the ## Unreleased section at the top of the changelog. Create the appropriate category heading if it doesn't exist yet. Entries are moved to a versioned section during the release process.
Examples
Good:
- "Added keyboard shortcuts for common actions"
- "Tasks now sync automatically when Obsidian starts"
- "Fixed tasks not appearing after editing"
Bad:
- "Refactored TaskStore to use Redux pattern with selectors"
- "Added
useEffecthook to trigger sync on mount" - "Fixed CSS specificity issue in task-list component"
Location
The changelog is located at docs/docs/changelog.md.
When not to use it
- →When documenting internal implementation details without user impact
Limitations
- →Limited to the changelog file located at docs/docs/changelog.md
How it compares
It mandates a user-centric focus, explicitly forbidding technical implementation details common in standard commit-based changelogs.
Compared to similar skills
write-changelog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| write-changelog (this skill) | 1 | 6mo | No flags | Beginner |
| ml-paper-writing | 48 | 6mo | Review | Advanced |
| docs-review | 10 | 7mo | No flags | Beginner |
| claude-md-improver | 21 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jamiebrynes7
View all by jamiebrynes7 →You might also like
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.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
update-docs
vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.