- Home
- Skills
- Technical Documentation
- Changelog Generator Pro
Works with the AI Agents you already use
Changelog Generator Pro
Turn Git history into structured changelogs with SemVer bump suggestions and breaking change detection.
$5
Changelog Generator Pro
Example session with this skill installed
Generate a markdown changelog for project 'hydra-api' from the last 5 commits: feat(auth)!: add oauth2 support, fix(db): resolve connection leak, perf: optimize query cache, docs: update readme.
- Read your context and instructions
- Compiled the changelog generator pro
The commit history for 'hydra-api' has been analyzed across 4 unique entries. One breaking change was identified, triggering a Major version recommendation.
Release Scope
- Project: hydra-api
- Commit Range: Last 5 commits (4 unique messages provided)
- Previous Version: 1.2.0 (Assumed)
Commit Classification
- Features: add oauth2 support (auth)
- Bug Fixes: resolve connection leak (db)
- Performance: optimize query cache
- Documentation: update readme
Breaking-Change Review
Confirmed: feat(auth)!: add oauth2 support. The ! marker indicates a breaking change in the authentication layer.
SemVer Recommendation
- Suggested Bump: MAJOR
- Proposed Version: 2.0.0
- Rationale: Presence of a breaking change in a stable (1.x) release requires a major version increment.
- Confidence: High
Changelog
hydra-api Release Notes
⚠️ Breaking Changes
- auth: add oauth2 support (Breaking Change)
Features
- auth: add oauth2 support
Bug Fixes
- db: resolve connection leak
Performance Improvements
- optimize query cache
Documentation
- update readme
Next steps
- Review the "auth" breaking change for migration impact.
- Verify version 2.0.0 aligns with your current tagging strategy.
- Copy the Markdown output into your RELEASE.md or GitHub Release page.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual changelog creation is slow and prone to missing breaking changes. This skill automates the transition from raw Git history to structured, release-ready documentation.
What it does
- Commit parsing identifies Conventional Commit structures including type, scope, and breaking change markers.
- Breaking change detection flags potential API-breaking updates using
!markers orBREAKING CHANGEfooters. - SemVer analysis suggests a version bump (Major, Minor, or Patch) based on the analyzed commit history.
- Categorized grouping organizes updates into Features, Fixes, Performance, and Maintenance sections.
- Multi-format export generates both polished Markdown for human reading and valid JSON for automated pipelines.
How it works
- Define range by providing the base and head commits, tags, or a specific date range.
- Process history through the commit parser to classify entries by type and impact.
- Review impact by examining the suggested SemVer bump and identified breaking changes.
- Output results in Markdown or JSON format for review or integration.
Frameworks & tools
This skill works with any Git-based project using Conventional Commits. It outputs standard Markdown and JSON compatible with GitHub, GitLab, and CI/CD automation tools.
Why this beats prompting it yourself
Generic prompts often hallucinate commit hashes or miss subtle breaking change indicators in footers. This skill follows strict logic to map every note to a real commit while enforcing SemVer precedence rules.
Use cases
- Generate release notes for a GitHub release or project README.
- Produce machine-readable JSON for internal deployment dashboards.
- Audit a commit range to determine if the next version should be a Major or Minor bump.
- Summarize documentation and maintenance work for stakeholders.
Known limitations
The quality of output depends entirely on the clarity of the provided commit history. It cannot verify if a code change is actually breaking if the commit message does not follow conventions.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires commit history to be provided or accessible via tools. Accuracy depends on Conventional Commit usage. Does not perform actual Git operations like tagging or pushing.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 18 days ago
Permissions
No special permissions declared or detected