Conventional Commits

    1

    Commit messages, PR titles and changelog entries that follow Conventional Commits 1.0, every time.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Conventional Commits

    Example session with this skill installed

    I just added a new column called dismissed_at to the signal table and created a use case to handle it. Write a commit message for this.

    • Read your context and instructions
    • Compiled the conventional commits

    I have drafted a conventional commit message for your changes to the signal module.

    Commit Message

    feat(signal): add dismissed_at column and dismiss use case
    
    Adds a new timestamp column to the signal table to track when a user
    dismisses a notification. The associated use case handles the
    persistence logic and ensures the dismissed state is reflected in
    downstream queries.
    
    Refs #42
    

    Next steps

    1. Run git commit -m followed by the message above.
    2. Verify the signal scope matches your project's naming convention for the backend layer.
    3. Ensure no other logical changes (like bug fixes) were included in this specific commit.

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

    About this skill

    Git history becomes a mess when every developer uses a different naming convention. This skill enforces the Conventional Commits 1.0 standard to ensure your logs remain readable, searchable, and compatible with automated tooling.

    What it does

    • Standardizes types by mapping changes to specific categories like feat, fix, refactor, or chore.
    • Enforces formatting including imperative mood, lowercase subjects, and character limits.
    • Identifies scopes to clearly mark which module or feature a commit affects.
    • Structures bodies to focus on the "why" behind a change rather than the "what".
    • Flags breaking changes using both the ! subject modifier and the BREAKING CHANGE: footer.

    How it works

    1. Analyze changes: Provide a diff or describe the work completed.
    2. Select type and scope: The skill maps the work to the correct conventional category.
    3. Draft message: It generates a subject line under 72 characters and an optional explanatory body.
    4. Review and refine: Compare the draft against the checklist for imperative mood and logical separation.

    Frameworks & tools

    This skill follows the Conventional Commits 1.0 specification. It is compatible with any git-based workflow and tools that consume conventional logs, such as semantic-release, standard-version, and automated changelog generators.

    Why this beats prompting it yourself

    Writing consistent commit messages manually is prone to "lazy" descriptions like "updated files." This skill provides a strict reference for type mapping and formatting rules that most general-purpose prompts overlook, such as DCO sign-offs and proper breaking change markers.

    Use cases

    • Drafting clean commit messages for complex multi-file refactors.
    • Standardizing PR titles to ensure squash-merges maintain a readable log.
    • Generating structured entries for automated changelog tools.
    • Auditing existing commit drafts to ensure they follow repo standards.

    Known limitations

    This skill does not interact with the git CLI directly. It generates the text for you to paste into your terminal or IDE.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.

    Text-based generation only; no direct git CLI execution. Focuses on Conventional Commits 1.0 standards. Logic changes incorrectly labeled as 'style' will be flagged.

    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

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 28 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Terminal / Shell
    Listed28 days ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the process of mapping code changes to the correct Conventional Commits 1.0 categories (like feat, fix, or chore) while ensuring strict adherence to formatting rules like character limits and imperative mood.

    The skill is a standardized prompt configuration compatible with leading AI agents such as ChatGPT, Claude, and Gemini; it works by analyzing the code diffs or descriptions you provide.

    No, this skill functions as a logic-based generator that provides formatted text for you to review and paste into your terminal, IDE, or PR title field.

    Yes, the skill is specifically designed to recognize breaking changes and will automatically format the output using the '!' modifier and the 'BREAKING CHANGE:' footer for compatibility with automated release tools.

    You will receive the specialized prompt architecture and a guide on how to deploy it within your preferred AI agent to start generating standardized commit messages immediately.

    New in Prompt & Skill Engineering

    Free