name	commit
description	Create conventional commit messages without co-author labels. Use when committing code changes or formatting git history.
metadata	{"version":"1.0.0"}

Conventional Commit

Create conventional commit messages following the Conventional Commits specification. Never add co-author labels.

Format

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

<body>

Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`refactor`	Code restructuring (no behavior change)
`docs`	Documentation only
`style`	Formatting, whitespace (no code change)
`test`	Adding or fixing tests
`chore`	Build, CI, tooling, dependencies
`perf`	Performance improvement

Scope (optional)

Use the affected package or module as scope, matching this repo's conventions. Common scopes:

Package names: console-ui, console-server, cloud-router, ai-engineer, sheets-ui
Subsystems: billing, scheduler, auth, mcp
Use the scope from recent commits when in doubt — run git log --oneline -20 to check

Rules

No co-author labels — never add Co-Authored-By lines
Subject line: imperative mood, lowercase, no period, max 72 chars
Body: explain why, not what. Wrap at 80 chars
One logical change per commit — split unrelated changes
Match the project's existing commit style (check recent history)

Steps

Run git status and git diff --cached to see staged changes
If nothing is staged, stage the relevant files (prefer specific files over git add -A)
Analyze the changes and determine the appropriate type and scope
Draft a concise commit message

Create the commit using a HEREDOC for proper formatting:

git commit -m "$(cat <<'EOF'
type(scope): subject line here

Optional body explaining why this change was made.
EOF
)"

Run git status after to verify

Examples

feat(console-ui): add group chat with realtime subscriptions

fix(console-server): correct next_run calculation for scheduled reports

refactor(cloud-router): merge mcp server into main binary

chore: update ui-kit to v0.15.0 across packages

fix(ai-engineer): handle token limit exceeded in streaming response

perf(billing): batch usage dimension writes to reduce DB round-trips

Conventional Commit

Create conventional commit messages following the Conventional Commits specification. Never add co-author labels.

Format

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

Types

Type

Purpose

feat

New feature

fix

Bug fix

refactor

Code restructuring (no behavior change)

docs

Documentation only

style

Formatting, whitespace (no code change)

test

Adding or fixing tests

chore

Build, CI, tooling, dependencies

perf

Performance improvement

Scope (optional)

Use the affected package or module as scope, matching this repo's conventions. Common scopes:

Package names: console-ui, console-server, cloud-router, ai-engineer, sheets-ui

Subsystems: billing, scheduler, auth, mcp

Use the scope from recent commits when in doubt — run git log --oneline -20 to check

Rules

No co-author labels — never add Co-Authored-By lines

Subject line: imperative mood, lowercase, no period, max 72 chars

Body: explain why, not what. Wrap at 80 chars

One logical change per commit — split unrelated changes

Match the project's existing commit style (check recent history)

Steps

Run git status and git diff --cached to see staged changes

If nothing is staged, stage the relevant files (prefer specific files over git add -A)

Analyze the changes and determine the appropriate type and scope

Draft a concise commit message

Create the commit using a HEREDOC for proper formatting:

git commit -m "$(cat <<'EOF'
type(scope): subject line here

Optional body explaining why this change was made.
EOF
)"

Run git status after to verify

Examples

feat(console-ui): add group chat with realtime subscriptions fix(console-server): correct next_run calculation for scheduled reports refactor(cloud-router): merge mcp server into main binary chore: update ui-kit to v0.15.0 across packages fix(ai-engineer): handle token limit exceeded in streaming response perf(billing): batch usage dimension writes to reduce DB round-trips

commit

Conventional Commit

Format

Types

Scope (optional)

Rules

Steps

Examples

同仓库更多 Skills

同仓库更多 Skills

Conventional Commit

Format

Types

Scope (optional)

Rules

Steps

Examples