Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Changelog Generator: Release Notes in Seconds

    1

    It sifts through git history and merged PRs to build structured changelogs that follow industry standards.

    Free

    7 uses5.0 (1 review)
    Changelog Generator: Release Notes in Seconds

    Changelog Generator: Release Notes in Seconds

    Example session with this skill installed

    Generate release notes for changes since v1.2.0. Focus on the new payment gateway and fix for the login timeout. We need a version bump recommendation too.

    • Read your context and instructions
    • Compiled the changelog generator

    I have analyzed the 14 commits and 2 merged PRs since v1.2.0. I found one new feature and one critical bug fix, along with several dependency updates. Based on the addition of a new feature without breaking changes, I recommend a

    Minor version bump to

    v1.3.0.

    Release Assets

    CHANGELOG.md Entry

    
    ## [1.3.0] - 2024-05-22
    ### Added
    - **payments:** Support for Stripe integration allowing multi-currency checkout flows (#442)
    
    ### Fixed
    - **auth:** Resolved a race condition causing session timeouts during high-latency login requests (#445)
    
    ### Internal
    - Updated 8 dependencies including `security` patches for `alpha-lib`.
    

    GitHub Release Notes

    🚀 Highlights

    This release introduces our highly requested Stripe payment gateway, enabling global transactions in over 135 currencies. We also addressed a session stability issue for users on slower connections.

    What's Changed

    • Added: Multi-currency support via Stripe (#442) @dev-pro-1
    • Fixed: Login timeout race condition (#445) @junior-fixer

    Full Changelog: https://github.com/org/repo/compare/v1.2.0...v1.3.0

    Social Announcement

    🚢 New Release: v1.3.0
    We just launched Stripe support for multi-currency checkouts! This update also includes a critical fix for login stability. Check out the full notes here: [Link]

    Next steps

    1. Review the generated notes for any missing internal context.
    2. Run git tag v1.3.0 and git push --tags to finalize.
    3. Use gh release create v1.3.0 to publish the GitHub release.
    CHANGELOG.md

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

    About this skill

    Writing release notes from raw git logs is tedious and prone to missing critical user-facing impacts. This skill automates the transition from technical commits to polished, public-facing documentation. It sifts through git history and merged PRs to build structured changelogs that follow industry standards.

    What it does

    • Commit classification groups changes into standardized sections like Added, Fixed, Security, and Breaking based on Conventional Commits and PR labels.
    • User-centric rewriting converts technical implementation details into benefit-driven feature descriptions.
    • Version inference analyzes the impact of changes to suggest the next SemVer version bump.
    • Metadata linking automatically attaches PR numbers and recognizes first-time contributors.
    • Multiformat output generates CHANGELOG.md entries, GitHub Release notes, and short social announcements simultaneously.

    How it works

    1. Identify the range by locating the last tag or a specific commit hash to determine what has changed since the last release.
    2. Collect data from git logs and the GitHub CLI, prioritizing PR descriptions and labels over raw commit messages for better context.
    3. Draft the content by filtering out internal noise like CI/CD tweaks or style changes while highlighting breaking migrations.
    4. Finalize and publish by prepending the official CHANGELOG.md and, if requested, executing the version bump and tag creation.

    Frameworks & tools

    This skill utilizes the GitHub CLI (gh), Git, and follows the "Keep a Changelog" and Semantic Versioning (SemVer) specifications.

    Why this beats prompting it yourself

    Generic prompts often include internal "chore" commits or fail to identify breaking changes hidden in commit footers. This skill specifically looks for BREAKING CHANGE markers and prioritizes PR context, ensuring your public notes are accurate and free of developer-only noise.

    Use cases

    • Generate a user-facing CHANGELOG.md entry before a major production deployment.
    • Draft GitHub release notes that highlight contributors and migration steps.
    • Create a concise Slack or social media update for a new feature launch.
    • Determine if a set of finished features requires a Minor or Major version bump.

    Known limitations

    Requires a git repository with a consistent tagging history. The GitHub CLI must be authenticated to fetch PR metadata. Internal refactors without visible effects are excluded by design.

    Requires git and GitHub CLI (gh) with valid authentication. Performs best with Conventional Commits. Does not generate notes for uncommitted local 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

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    This skill has been used 7 times.

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Requires

    Git

    Permissions

    Terminal / Shell
    Write Files
    Listed7 days ago
    Updated6 days ago

    What's inside

    Frequently Asked Questions

    The skill filters out 'noise' like CI/CD tweaks and internal refactors, focusing instead on user-facing impacts and breaking changes defined by Conventional Commit standards. It prioritizes pull request descriptions over raw commit logs to ensure the output reads like documentation rather than a technical log.

    This skill is compatible with any AI agent that has access to your local environment or repository and supports the GitHub CLI (gh). It requires a git-based repository and functions best when the project follows SemVer tagging and Conventional Commit naming conventions.

    Yes, the skill is designed to analyze the weight of your changes—such as identifying 'BREAKING CHANGE' footers—to suggest whether your next release should be a Major, Minor, or Patch version according to Semantic Versioning rules.

    You receive the complete skill configuration and logic required to integrate this workflow into your AI agent. This includes the structured instructions for data collection via the GitHub CLI and the templates for generating multi-format outputs like CHANGELOG.md and social announcements.

    Setup is minimal; you only need to ensure your AI agent has permission to run git and GitHub CLI commands within your repository. Once authenticated, the skill can automatically identify the range between your last tag and your current HEAD to begin drafting notes.

    New in Technical Documentation