More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    📝 Changelog Generator

    2

    Use an explicit two- or three-dot range, a bounded recent-commit count, a reachable tag comparison, or the default nearest-tag-to-HEAD selection.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    📝 Changelog Generator

    📝 Changelog Generator

    Example session with this skill installed

    Generate plain Markdown release notes for the commits since the nearest reachable tag. Keep malformed commits visible, flag breaking changes from headers or footers, and suggest—but do not apply—the next SemVer version.

    • Read your context and instructions
    • Compiled the changelog generator

    Illustrative output structure

    The actual result is generated from your repository, not from this example.

    
    # Release Notes: Unversioned
    
    Requested selection: an explicit commit range
    Resolved selection: the verified commit IDs
    Commits analyzed: the number actually selected
    
    ## Features
    - A feature supported by a selected commit, with its short hash.
    
    ## Fixes
    - A fix supported by a selected commit, with its short hash.
    

    Unknown or malformed commit subjects are retained under Chores. A Breaking Changes section appears only for recognized author markers outside excluded examples. Explicit historical ranges do not establish a next release version. The agent returns the Markdown for review and creates a new file only when requested; it does not overwrite existing files or publish a release.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Release notes from verified local history

    Changelog Generator reads a local Git repository and returns plain Markdown notes with commit IDs and a resolved selection. Use an explicit two- or three-dot range, a bounded recent-commit count, a reachable tag comparison, or the default nearest-tag-to-HEAD selection. Tagless default selections fall back to 20 commits.

    What you get

    A bundled Python helper, agent instructions, formatting reference and regression tests. Conventional Commit categories are grouped; unknown or malformed subjects remain visible. Breaking markers are author-provided signals, not proof of API incompatibility. Quoted, fenced and indented examples are excluded. An unclosed fence keeps subsequent text inside the example.

    Version and output boundaries

    A next-version suggestion requires a nonempty default unreleased selection with a stable SemVer base. Historical ranges, count windows, tag comparisons and unsupported bases return Unversioned. Maintainers decide the release version. Existing files are never overwritten; output requires an explicitly requested new path. Paths through symlinks or junctions are refused, including linked parent folders. Relative output paths use the current working directory.

    Requirements and limits

    Requires Python, Git in PATH and an agent host able to execute the bundled helper against an authorized local repository. Reads local commit metadata without network access, fetching, pushing, tagging or publication. Large histories can take minutes. Ambiguous refs and observed tag changes stop the run. No guarantee is made against concurrent adversarial filesystem changes. Tested with synthetic Windows and Linux repositories; platform-specific test limits remain documented.

    Price and existing commercial terms are unchanged.

    Author markers are not proof of compatibility. Only nonempty default unreleased selections with a stable SemVer base receive a suggestion; historical/count/tag comparisons return Unversioned. Fenced or indented examples are excluded; unclosed fences may hide intended footers. Existing output files and paths through any symlink/junction ancestor are refused. Large histories can take minutes. No network, release publication, diff analysis or guarantee against concurrent adversarial filesystem changes.

    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 16 days ago

    Requires

    Python
    Git
    Agent host with local terminal execution

    Permissions

    Terminal / Shell
    Write Files
    Read Files

    File Scopes

    CHANGELOG.md

    Reads local Git commit metadata and bundled instructions through terminal execution. Optional writing creates a new user-requested Markdown file only; existing files and linked output paths are refused. No fetch, push, release publication, network, credentials or environment-variable access.

    Listed5 months ago
    Updated16 days ago

    What's inside

    Frequently Asked Questions

    Only a nonempty default unreleased selection with a stable SemVer base gets a suggestion: recognized breaking markers suggest major, features minor, otherwise patch. Historical ranges, counts, tag comparisons and unsupported bases return Unversioned. Maintainers decide compatibility and release policy.

    Yes. Recognized types are grouped normally, while unknown, empty, merge-like, revert-like, and malformed subjects remain visible under Chores instead of being dropped.

    Use a fully specified two- or three-dot range, a last-N count from 1 to 100000, or a uniquely ancestry-ordered pair of reachable tags. Default uses the nearest reachable tag to pinned HEAD, with a 20-commit fallback when tagless. Ambiguous names or tag pairs stop for clarification.

    Plain UTF-8 Markdown with stable text headings, a range and commit-count summary, grouped bullets, short hashes, breaking changes, and a SemVer suggestion. It does not depend on emoji rendering.

    Conventional Commit ! headers and nonempty BREAKING CHANGE: or BREAKING-CHANGE: footer-style lines are author signals. Quoted, fenced and four-space/tab-indented examples are excluded. An unclosed fence keeps subsequent lines inside the example. Markers do not prove actual API incompatibility.

    The helper requires Python 3.9+ and Git in PATH. It reads local commit metadata only and does not fetch, pull, push, tag, commit, publish, inspect diffs/files, read credentials, or use the network.

    New in Technical Documentation