Global AI chat room · 15 online now Join now
C
SKILL Listed

Conventional Commit Message Generator

A reusable Coding skill centered on Conventional Commit Message Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.

jeff-nasseriCodingCoding
4.1Rating
16.1KUses
—Feedback
01 / SKILL INTRODUCTION

About this skill

A reusable Coding skill centered on Conventional Commit Message Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.

TRIGGER DESCRIPTION

Use this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable Coding skill centered on Conventional Commit Message Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.

01Progressive disclosure

Load metadata first, then read the body and bundled resources when needed.

02Evaluable iteration

Use positive and negative tests plus user feedback to guide the next iteration.

03Clear output contract

Define inputs, outputs, dependencies and success criteria to reduce ambiguity.

02 / SKILL FILES

Skill files

SKILL.mdMarkdown · — · Previewable
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The outpu
This is an online preview. Copy it and continue editing in your local skill directory.
YAML FRONTMATTERSkill metadata
nameConventional Commit Message Generator
descriptionUse this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable Coding skill centered on Conventional Commit Message Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
03 / WORKFLOW

How to use

  1. 01
    Step 1

    Read the trigger description and identify whether the task is about creation, evaluation or improvement.

  2. 02
    Step 2

    Open SKILL.md and confirm the input, output and bundled resource requirements.

  3. 03
    Step 3

    Run a small test set with realistic positive and negative prompts.

  4. 04
    Step 4

    Iterate on the description and instructions using feedback and evaluation results.

04 / DISCUSSIONS

Discussions and feedback

—feedback records

Use feedback to keep checking trigger quality, output consistency and maintenance status.

Back to skills
Email