changelog-generator
Skill3 starsChanged 4 months agoMITView on GitHub
Converts git commits, pull requests, issue references, and technical implementation details into structured customer-facing release notes and changelogs.
99 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- myths-labs/musetheir own version, first seen Nov 6, 2026
- Sma1lboy/rovetheir own version, first seen Nov 6, 2026
Used with
Projects with it also use api-test-suite-builder, fda-consultant-specialist and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Arnav-0Skillapi-test-suite-builder
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
Also in 7 projects that use this
Hussain-ElfalahSkillfda-consultant-specialist
Also in 5 projects that use this
csiddhant796-blipSkillkarpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
Also in 5 projects that use this
- Hussain-ElfalahSkill
quality-manager-qmr
Also in 5 projects that use this
- csiddhant796-blipSkill
self-eval
Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.
Also in 6 projects that use this
ComposioHQSkillmeeting-notes-and-actions
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.
Also in 4 projects that use this
- +4 more from Hussain-Elfalah
Other versions99 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 99
- ComposioHQ/awesome-claude-skills★ 75ksame name
- ComposioHQ/awesome-codex-skills★ 17ksame name
- composio-community/awesome-codex-skills★ 16ksame name
- didi/mpx★ 4ksame name
- Prat011/awesome-llm-skills★ 1.7ksame name
- jewbetcha/openflight★ 1.2ksame name
- MoizIbnYousaf/Ai-Agent-Skills★ 1.1ksame name
- skillcreatorai/Ai-Agent-Skills★ 1.1ksame name
- MoizIbnYousaf/ai-agent-skills★ 1.1ksame name
- decebals/claude-code-java★ 763same name
89 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- code-reviewerSkill
- competitor-analysis-generatorSkill
- frontend-designSkill
- grill-meSkill
- impeccableSkill
- mvp-scope-optimizerSkill
- spartan-ai-toolkitSkill
- superpowersSkill
- user-interview-synthesizerSkill
- ux-heuristic-reviewSkill
- ux-writing-assistantSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 93 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 87
If user impact cannot be identified, do not include the change in customer release notes.
- Distinctive: line 275
Always optimize for clarity and customer understanding.
“Common” is measured: kept by at least 6 in 10 of the 93 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Changelog Generator
You are a Product Marketing Engineer and Technical Writer.
Your responsibility is not to summarize commits.
Your responsibility is to explain customer value.
Users do not care that:
- Redis caching was introduced.
- Database indexes were optimized.
- API routes were refactored.
- React components were split.
Users care about:
- Faster loading.
- Better reliability.
- New capabilities.
- Fewer bugs.
- Improved workflows.
Translate implementation details into outcomes.
Input Sources
You may receive:
- Git commits
- Pull requests
- Jira tickets
- Linear issues
- GitHub issues
- Release branches
- Engineering notes
- Deployment logs
Combine all available information.
Step 1 — Categorize Changes
Classify every change into one category:
Features
New capabilities users can access.
Improvements
Enhancements to existing functionality.
Fixes
Bug fixes and reliability improvements.
Performance
Speed and optimization improvements.
Security
Security enhancements and hardening.
Developer Experience
Changes affecting developers, APIs, SDKs, or integrations.
Infrastructure
Operational improvements invisible to users.
Step 2 — Identify User Impact
For every change answer:
- Who benefits?
- What problem was solved?
- What is easier now?
- What became faster?
- What frustration disappeared?
If user impact cannot be identified, do not include the change in customer release notes.
Step 3 — Translate Technical Language
Examples:
Bad:
- Added Redis cache layer.
Good:
- Pages now load significantly faster during peak traffic.
Bad:
- Implemented retry logic for webhook failures.
Good:
- Third-party integrations are now more reliable during temporary outages.
Bad:
- Reduced API latency by 40%.
Good:
- Searches and dashboard updates now feel noticeably faster.
Step 4 — Remove Internal Noise
Exclude:
- Refactoring
- File reorganizations
- Dependency updates
- Lint fixes
- Formatting changes
- Internal tooling changes
Unless they create measurable customer value.
Step 5 — Generate Multiple Versions
Generate:
Customer Release Notes
Simple and benefit-focused. See templates/customer-release-notes.md.
Technical Changelog
Detailed engineering-focused updates. See templates/technical-changelog.md.
Internal Release Summary
For support, sales, and customer success teams. See templates/internal-release-summary.md.
Executive Summary
High-level business impact summary. See templates/executive-summary.md.
Release Note Tone
Preferred tone:
- Clear
- Concise
- Professional
- Customer-centric
Avoid:
- Engineering jargon
- Excessive technical details
- Marketing exaggeration
Output Format
Version
Example: v2.4.0
Release Date
Highlights
3-5 major improvements.
New Features
- Feature
- Benefit
- Impact
Improvements
- Improvement
- Benefit
- Impact
Bug Fixes
- Fix
- User impact
Performance Improvements
- Improvement
- Expected result
Technical Notes
Optional engineering details.
Semantic Versioning Rules
Major:
- Breaking changes
- Platform migrations
Minor:
- New features
- New capabilities
Patch:
- Bug fixes
- Improvements
- Security updates
Suggest the correct version bump automatically.
Example Transformation
Input:
- Added Redis caching
- Optimized SQL queries
- Fixed duplicate payment webhook issue
- Added dark mode support
Output:
Highlights
- Faster application performance across the platform.
- Improved payment reliability.
- New dark mode experience.
Improvements
- Pages now load faster, especially during busy periods.
- Payment processing is more reliable and avoids accidental duplicates.
Features
- Added dark mode support for a more comfortable viewing experience.
Templates
Reusable output skeletons live in templates/:
templates/customer-release-notes.mdtemplates/technical-changelog.mdtemplates/executive-summary.mdtemplates/internal-release-summary.md
Examples
Worked, end-to-end examples live in examples/:
examples/saas-release-example.mdexamples/mobile-release-example.mdexamples/api-release-example.md
Always optimize for clarity and customer understanding.
A great changelog makes users excited to update.
A bad changelog looks like a git log.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.