Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Conventional Commit Writer

    1

    This skill reads your **staged** diff and produces a spec-correct Conventional Commits message.

    $3

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Conventional Commit Writer

    Example session with this skill installed

    write a commit message for my staged changeswrite a commit message for my staged changes

    • Read your context and instructions
    • Compiled the conventional commit writer

    feat(auth): add refresh-token rotation

    Short-lived access tokens now rotate their refresh token on every use, so a leaked refresh token is usable at most once.

    Closes #214

    Then run
    git commit -F - <<'EOF'
    ...message above...
    EOFa fenced Conventional Commit message + the git commit -F - command to apply it.

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

    About this skill

    Conventional Commit Writer

    A clean commit history without hand-crafting every message. This skill reads your staged diff and produces a spec-correct Conventional Commits message.

    What it does

    • Picks exactly one correct type (feat, fix, refactor, perf, docs, ...) from the diff
    • Infers an optional scope from the paths you touched
    • Writes a <=50-char imperative subject + a why-focused wrapped body
    • Adds the right footers: BREAKING CHANGE (with !), Closes #N when the issue is evident
    • Recommends splitting the commit when the diff mixes unrelated concerns

    Read-only by design. It prints the final message and the exact git commit command. You run it. It never commits, stages, or rewrites history.

    Why buy it: consistent history that feeds semantic-release / release-please / git-cliff, enforced across a team, with zero mental overhead per commit.

    Read-only mode requires manual execution of the commit. Requires staged changes to function. Cannot invent issue numbers or scopes without evidence in the diff or branch name.

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

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the creation of standardized commit messages by analyzing your staged changes, ensuring your repository remains compatible with automated tools like semantic-release without requiring manual formatting.

    The skill is designed to work with any AI agent capable of executing terminal commands and reading file diffs, specifically those with access to your local git environment.

    No, for security and control, the skill generates the formatted command and message for your review; you retain final authority to execute the commit in your terminal.

    Yes, the skill is programmed to detect breaking changes and include the required 'BREAKING CHANGE:' footer, ensuring your automated versioning tools correctly trigger a major SemVer bump.

    The skill requires an active Git repository and only analyzes changes that have been added to the staging area via 'git add' before execution.

    New in Code Quality & Review