commit

Files (1)

• SKILL.md

SKILL.md (first lines)

# Git Commit with Conventional Commits

## Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

## Conventional Commit Format

```
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

The parts marked as <description>, [optional body], and [optional footer(s)] MUST be filled in Chinese.

## Hook Prefix Composition Rule

This skill generates only the Conventional Commit suffix:

```
<type>[optional scope]: <description>
```

Do NOT generate `CPST-` or `CPED-` in this skill output.

- Hook-triggered auto commits: hooks/scripts prepend `CPST-` / `CPED-` automatically.
- Manual `/commit`: no automatic CP prefix is added.
- Final message for hook-triggered commits is composed as:
	- `<hook-prefix>-` + `<skill-generated conventional suffix>`
	- Example: `CPED-` + `feat: 增加了轮速补偿` -> `CPED-feat: 增加了轮速补偿`

## Commit Types

| Type       | Purpose                              |
| ---------- | ------------------------------------ |
| `feat`     | New feature                          |
| `fix`      | Bug fix                              |
| `docs`     | Documentation only                   |
| `style`    | Formatting/style (no logic)          |
| `refactor` | Code refactor (no feature/fix)       |
| `perf`     | Performance improvement              |
| `test`     | Add/update tests                     |
| `build`    | Build system/dependencies            |
| `ci`       | CI/config changes                    |
| `chore`    | Maintenance/misc                     |
| `revert`   | Revert commit                        |
| `add`      | Add new files/resources              |
| `del`      | Delete files/code                    |
| `tmp`      | Temporary commit (for test/save)     |

## Breaking Changes

```
# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed
```

## Workflow

### 1. Analyze Diff

```bash
# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain
```

### 2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

```bash
# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p
```

**Never commit secrets** (.env, credentials.json, private keys).

### 3. Generate Commit Message

Analyze the diff to determine:

- **Type**: What kind of change is this?
- **Scope**: What area/module is affected?
- **Description**: One-line summary of what changed (present tense, imperative mood, <72 chars)

### 4. Execute Commit

```bash
# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>

From IHiter-2026-Wheeled-Bipedal-Soldier/Wheeled_Bipedal_Shared_CC_Config, MIT.

More from IHiter-2026-Wheeled-Bipedal-Soldier/Wheeled_Bipedal_Shared_CC_Config