Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Changelog Writer

    1

    Turn git diffs or a commit range into a clean, consumer facing API changelog, with breaking changes first and written for API consumers, not engineers.

    $4.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Changelog Writer

    Example session with this skill installed

    Review the changes in v1.1.0..v1.2.0 in the current repo and generate a changelog. Group breaking changes at the top.

    • Read your context and instructions
    • Compiled the changelog writer

    I have analyzed the diff between v1.1.0 and v1.2.0. I identified one breaking change and two feature additions. Internal refactors to the TokenValidator class were excluded from the consumer log.

    Breaking changes

    • POST /v2/orders now requires billing_address. Previously, this field was optional for guest checkouts.
      What this means for you: Requests without a billing_address body parameter will now return a 422 Unprocessable Entity error.
      Migration: Ensure your checkout flow collects and passes the billing_address object for all order types.

    [1.2.0] - 2023-11-15

    Added

    • GET /v2/products now supports category filtering.
      What this means for you: You can narrow down product lists by passing a category query parameter.
    • New discount_applied boolean in the Order response.
      What this means for you: Easily check if a coupon was successfully processed without calculating price differences.

    Fixed

    • Resolved an issue where DELETE /v2/cart would return a 500 error if the cart was already empty.

    Skipped (intentional, no consumer impact)

    • d4e5f6g internal: Refactored AuthMiddleware to use new caching layer.
    • a1b2c3d test: Added integration tests for webhook retries.

    Next steps

    • Review the Breaking changes section to ensure the migration note matches the intended deprecation path.
    • I recommend a Major version bump (2.0.0) because the billing_address requirement is a breaking contract change.
    • Run git tag v1.2.0 once you have verified the CHANGELOG.md update.

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

    About this skill

    Raw git logs and diffs are often noise-heavy, making it difficult for API consumers to identify what actually impacts their integrations. This skill automates the extraction of contract changes from your version history, translating technical commits into a structured, consumer-facing changelog. It identifies breaking changes, suggests SemVer increments, and writes migration notes so your users know exactly how to update their code.

    What it does

    • Extracts surface changes by scanning diffs for modifications to routes, request parameters, response shapes, status codes, and auth scopes.
    • Identifies breaking changes using a specialized radar to detect modifications that will fail existing valid requests.
    • Filters technical noise by automatically logging and excluding refactors, test updates, and internal-only dependency bumps.
    • Translates technical intent into consumer-facing language, replacing internal class names with public endpoint descriptions.
    • Generates SemVer recommendations based on the detected impact, specifically naming the change that forces a major, minor, or patch bump.

    How it works

    1. Ingest diffs from a pasted text block, a commit range (e.g., v1.2.0..HEAD), or a local repository path.
    2. Classify changes into the standard Keep a Changelog categories: Added, Changed, Deprecated, Removed, Fixed, and Security.
    3. Draft migration notes for every breaking change, providing clear instructions for consumers to follow.
    4. Append to file by merging the new release notes into your existing CHANGELOG.md or creating a new one.

    Frameworks & tools

    This skill utilizes git for history traversal and bash for diff collection. It is designed to work with any language or framework where the API surface is visible in the source code, including REST, GraphQL, and SDK-based projects.

    Why this beats prompting it yourself

    Generic prompts often leak internal implementation details or fail to recognize subtle breaking changes like modified default values. This skill uses a multi-step radar and specific voice guides to ensure every entry is relevant to an external developer while maintaining a strict audit trail of excluded commits.

    Use cases

    • Generating release notes for a public REST API before a production deployment.
    • Auditing a large pull request to identify undocumented breaking changes.
    • Maintaining a historical CHANGELOG.md in a monorepo by filtering for specific package paths.
    • Preparing migration guides for SDK version bumps.

    Known limitations

    The skill cannot verify breaking changes if the old behavior was undocumented or resides in external services. It requires access to the git binary or a pasted diff to function.

    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.

    Cannot prove breaking changes for undocumented side effects or external service behavior. Requires git binary access or manually pasted diffs. Large multi-release ranges must be split.

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

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed23 days ago

    What's inside

    Frequently Asked Questions

    The skill focuses on 'contract changes' like modified routes, parameters, and response shapes, while filtering out internal refactors and test updates that don't affect the end user.

    It is framework-agnostic and works with any language where API changes are visible in source code, including REST, GraphQL, and SDK-based projects.

    Yes, the skill is designed to analyze specific commit ranges (e.g., v1.1..v1.2) or localized paths, making it ideal for managing individual service logs within a monorepo.

    The skill utilizes a specialized 'breaking change radar' to detect modifications that invalidate existing requests and provides a recommended SemVer increment based on that impact.

    This skill requires a standard environment with `git` and `bash` access to traverse your history and collect diffs for analysis.

    New in Technical Documentation