Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Changelog Marketing

    1

    Extracts human-readable changelogs and launch notes from git commits while filtering out technical noise and fluff.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Changelog Marketing

    Changelog Marketing

    Example session with this skill installed

    Turn commits v1.0.0..v1.1.0 in ./repo into a changelog and launch note for product 'BoltDB'. Max 5 items, note under 100 words. Audience is existing users. No marketing fluff.

    • Read your context and instructions
    • Compiled the changelog marketing

    I have analyzed the commit range v1.0.0..v1.1.0 for BoltDB. I identified 3 user-facing changes and 1 breaking change. Technical refactors and CI updates were moved to the internal log.

    docs/changelog.md

    Header
    Product: BoltDB
    Version: v1.1.0
    Range: v1.0.0..v1.1.0
    Status: ready

    Source Notes
    Thesis: Improving query stability and disk space reclamation.
    Classified: 4 user-facing/breaking, 12 internal.

    Changelog

    Added

    • Implemented background compaction to reclaim unused disk space during idle periods.
    • Added support for read-only transactions on encrypted stores.

    Fixed

    • Resolved a race condition during concurrent bucket deletions.

    Breaking

    • The Open() function now requires a timeout context to prevent indefinite blocking.

    Launch Note
    Title: Reliable background compaction and stable concurrent transactions
    Body: This update focuses on the long-term health of your database files. BoltDB now automatically reclaims disk space in the background, preventing uncontrolled file growth. We have also hardened concurrent operations to eliminate rare race conditions during bucket management.
    Close: Update your dependency to v1.1.0 to start using these improvements.
    Word Count: 52

    Residual

    • published: no
    • posted: no
    • tagged: no
    • voice: not loaded
    • handle stripped: 2

    Next steps

    • Review the drafted docs/changelog.md file.
    • Copy the launch note into your release management tool.
    • Manually tag the v1.1.0 release in your repository.

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

    About this skill

    The problem

    Engineering commit logs are unreadable for customers, and manually drafting release notes is a repetitive chore. Developers often struggle to extract user-facing value from a wall of git SHAs and technical PR descriptions.

    What it does

    • Analyzes a specific git range or commit file to identify user-facing changes.
    • Classifies every commit as user-facing, internal, or breaking to filter technical noise.
    • Generates a grouped human-readable changelog (Added, Fixed, Security, etc.) without SHAs or handles.
    • Drafts a concise launch note for non-technical audiences based on a single frozen thesis.
    • Enforces strict word counts and item limits to keep release communication focused.

    Frameworks & tools

    Works with any project containing a git history or a flat file of commit/PR data. Uses git log for local repository reads and writes standardized Markdown to docs/changelog.md.

    Why this beats prompting it yourself

    Generic prompts often hallucinate features, use marketing fluff like "game-changer," or accidentally leak internal handles and developer SHAs. This skill uses a strict classification procedure and a banned-phrase list to ensure the output is professional, data-driven, and safe for public consumption.

    Use cases

    • Converting a sprint's worth of PRs into a customer-ready changelog.
    • Drafting the "What's New" paragraph for a version release.
    • Cleaning up internal commit subjects for an external status page.

    Known limitations

    Does not support external voice files to prevent prompt injection. Will not publish, tag, or post to social media. Requires a non-empty user-facing commit range to function.

    Will not load external voice files. Does not perform git tagging, publishing, or social media posting. Requires a defined git range or commit list to proceed.

    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 2 months ago

    Permissions

    Read Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill acts as a bridge between technical git history and customer-facing communication, filtering out internal jargon and technical noise to create readable Markdown changelogs and launch notes.

    The skill is compatible with any AI agent that has access to a file system or git CLI, as it reads commit data directly and writes formatted Markdown to your documentation directory.

    No, this skill is designed with a strict "banned-phrase" list and a classification procedure that prevents the inclusion of sensitive developer handles, SHAs, or internal-only PR descriptions in the final output.

    Setup is minimal; once the skill is added to your agent, you simply provide the git range or a file of PR descriptions, and the agent will automatically begin the classification and drafting process.

    Yes, you can enforce strict word counts and item limits to ensure your release notes remain concise and focused on the most impactful updates for your users.

    The skill produces a structured Markdown file (typically docs/changelog.md) and a separate concise launch note, ready to be copied into newsletters, status pages, or app store descriptions.

    New in Technical Documentation