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

Commit Message Preparation

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

[email protected]CodingCoding
4.3Rating
73Uses
—Feedback
01 / SKILL INTRODUCTION

About this skill

A reusable Coding skill centered on Commit Message Preparation. 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 Commit Message Preparation. 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
# Git Commit Guidelines for AI Language Models

## Core Principles

1. **Follow Conventional Commits** (https://www.conventionalcommits.org/)
2. **Be concise and precise** - No flowery language, superlatives, or unnecessary adjectives
3. **Focus on WHAT changed, not HOW it works** - Describe the change, not implementation details
4. **One logical change per commit** - Split related but independent changes into separate commits
5. **Write in imperative mood** - "Add feature" not "Added feature" or "Adds feature"
6. **Always include body text** - Never use subject-only commits

## Commit Message Structure

```
<type>(<scope>): <subject>

<body>

<footer>
```

### Type (Required)

- `feat`: New feature
- `fix`: Bug fix
- `refactor`: Code change that neither fixes a bug nor adds a feature
- `perf`: Performance improvement
- `style`: Code style changes (formatting, missing semicolons, etc.)
- `test`: Adding or updating tests
- `docs`: Documentation changes
- `build`: Build system or externa
This is an online preview. Copy it and continue editing in your local skill directory.
YAML FRONTMATTERSkill metadata
nameCommit Message Preparation
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 Commit Message Preparation. 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