More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Git Release Composer

    2

    Turns a diff into a changelog entry, with a matching commit message and PR description in the same pass — no git access needed.

    Free

    3 installs5.0 (1 review)
    Git Release Composer

    Git Release Composer

    Example session with this skill installed

    HHere's my diff — write a commit message, PR description, and changelog entry for it:

    diff --git a/src/api/orders.ts b/src/api/orders.ts

    • export function fetchOrder(id) {
    • return db.orders.findById(id);
    • }
    • export function getOrder(orderId, options = {}) {
    • return db.orders.findById(orderId, options);
    • }
    • Read your context and instructions
    • Compiled the git release composer

    Here's all three, generated from the diff:

    Commit message

    ​```
    refactor(orders)!: rename fetchOrder to getOrder, add options param

    fetchOrder is renamed to getOrder for consistency with other
    resource getters, and now accepts an options object for
    future extensibility.

    BREAKING CHANGE: fetchOrder(id) is removed. Replace calls
    with getOrder(orderId, options).
    ​```

    PR description

    ​```markdown

    What changed

    fetchOrder(id) is renamed to getOrder(orderId, options) and now
    takes an options object instead of a single positional argument.

    Why

    Aligns the naming and signature with the other resource getters
    (getUser, getInvoice).

    How to test

    Existing unit tests for fetchOrder were updated to call getOrder;
    run the orders test suite.

    Breaking changes

    fetchOrder is removed. All call sites must switch to
    getOrder(orderId, options).
    ​```

    Changelog entry

    ​```markdown

    Changed

    • fetchOrder(id) is renamed to getOrder(orderId, options) —
      update any direct calls
      ​```

    Next steps: paste the commit message into git commit, the PR
    description into your pull request, and the changelog entry into
    CHANGELOG.md under your next release heading. The breaking-change
    flag was detected automatically from the renamed export and changed
    signature — no need to call it out yourself.

    CHANGELOG.md

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

    About this skill

    Changelog entries always come last and always get written in a rush — different tone, different level of detail, often disconnected from what the commit message or PR description already said about the same change. Git Release Composer fixes that by generating all three from one pass over the diff, so they actually agree with each other.

    Paste a diff, a .patch file, or just describe what changed — the skill classifies the change (feat, fix, refactor, chore, etc.), detects breaking changes, and produces:

    • Changelog entry — Keep a Changelog format, user-facing language, no internal implementation detail
    • Commit message — Conventional Commits format, imperative summary, body explains why, breaking-change footer when applicable
    • PR description — What changed / Why / How to test / Breaking changes, with empty sections omitted rather than padded with "N/A"

    This is a pure text-generation skill: no git commands are run and no repository access is required. That makes it a fit for read-only agents, restricted environments, or anyone who just wants the words handed to them without any automation attached — a lighter-weight complement to full git-execution/code-review skills, not a replacement for one.

    Compatible with Claude Code, Cursor, Codex CLI, Gemini CLI, VS Code Copilot, and any other SKILL.md-compatible agent.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

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

    3 people have installed this skill.

    Trust & safety

    Security scanned

    Verified clean 28 days ago

    • Free to download with an account

    Needs access to

    Conventionalcommits
    Keepachangelog

    Listed28 days ago

    What's inside

    Frequently Asked Questions