Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Changelog Generator Pro

    1

    Turn Git history into structured changelogs with SemVer bump suggestions and breaking change detection.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Changelog Generator Pro

    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

    1. Review the "auth" breaking change for migration impact.
    2. Verify version 2.0.0 aligns with your current tagging strategy.
    3. Copy the Markdown output into your RELEASE.md or GitHub Release page.
    3. Copy the Markdown output into your RELEASE.md

    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 or BREAKING CHANGE footers.
    • 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

    1. Define range by providing the base and head commits, tags, or a specific date range.
    2. Process history through the commit parser to classify entries by type and impact.
    3. Review impact by examining the suggested SemVer bump and identified breaking changes.
    4. 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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    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

    Listed18 days ago
    Updated16 days ago

    What's inside

    Frequently Asked Questions

    The skill specifically looks for Conventional Commit patterns, such as '!' markers and 'BREAKING CHANGE' footers, to ensure versioning accuracy that manual prompting often overlooks.

    Yes, the skill is compatible with any Git-based project regardless of the programming language, provided your commit messages follow standard documentation conventions.

    The skill outputs a suggested version bump (Major, Minor, or Patch) by analyzing the hierarchy of changes within your specified commit range.

    Absolutely; it generates structured JSON outputs designed specifically for integration into automated CI/CD pipelines or custom deployment dashboards.

    You receive the full skill logic and documentation for deployment within your AI agent environment, including support for both Markdown and JSON export formats.

    The skill relies on the text within your Git history; if a breaking change is not documented in the commit message, the tool cannot independently verify code-level API shifts.

    New in Technical Documentation