commit-ai

Files (1)

• SKILL.md

SKILL.md (first lines)

# Commit (Atomic, AI-attributed)

## Overview

Same as `/commit` — atomic conventional commits — **but every message ends with a `Co-Authored-By` footer marking it as AI-assisted**.

## Conventional Commit Format

```
<type>: <description>

[optional body]

Co-Authored-By: <MODEL_NAME> <noreply@anthropic.com>
```

No scope. Footer always present.

**`<MODEL_NAME>` is dynamic** — substitute the assistant's currently running model at commit time (e.g. `Claude Opus 4.7 (1M context)`, `Claude Sonnet 4.6`, `Claude Haiku 4.5`). Read it from the runtime environment; never hardcode.

## 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                  |

## Breaking Changes

```
feat!: remove deprecated endpoint

Co-Authored-By: <MODEL_NAME> <noreply@anthropic.com>
```

or with body:

```
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Co-Authored-By: <MODEL_NAME> <noreply@anthropic.com>
```

## Workflow

### 1. Analyze Diff

```bash
git status --porcelain
git diff
git diff --staged
```

Stage only files touched in this session.

### 2. Group Into Atomic Commits

One logical change per commit. Use `git add -p` for files with mixed work; verify with `git diff --cached`.

```bash
git add path/to/file1 path/to/file2
```

Never `git add -A` or `git add .`. **Never commit secrets.**

### 3. Generate Commit Message

- **Type**: see table
- **Description**: present tense, imperative, **< 72 chars**
- Body only when *why* is non-obvious
- **Footer always present** with current model name

### 4. Execute Commit (HEREDOC for footer)

```bash
git commit -m "$(cat <<'EOF'
<type>: <description>

Co-Authored-By: <MODEL_NAME> <noreply@anthropic.com>
EOF
)"
```

With body:

```bash
git commit -m "$(cat <<'EOF'
<type>: <description>

<body explaining why>

Co-Authored-By: <MODEL_NAME> <noreply@anthropic.com>
EOF
)"
```

Resolve `<MODEL_NAME>` to the actual running model before executing the `git commit`. Do not commit the literal placeholder.

Repeat steps 2–4 per group.

## Best Practices

- One logical change per commit
- Present tense, imperative mood
- Subject under 72 characters
- Reference issues when relevant: `Closes #123`
- Most commits are subject + footer only (no body)

From PinpongTp/dotclaude, MIT.

More from PinpongTp/dotclaude