commit-disciplinelisted
Install: claude install-skill voidcorp-core/void-harness
# commit-discipline — voidcorp craftsman edition
The git log is the project's living narrative. "fix stuff" / "wip" / "asdf" destroy that narrative. Conventional Commits give shape; the mandatory "why" in the body gives substance. This skill enforces both.
**Attribution**: see `.source`. Foundation: Conventional Commits spec + Folpe "always say why" + citypaul commit guidance.
---
## Format
```
<type>(<scope>): <subject>
<blank line>
<body explaining WHY — the rationale, the constraint, the spec link>
<blank line>
<footers — BREAKING CHANGE, Co-Authored-By, Closes #N>
```
### Types (allowed list)
| Type | When |
|---|---|
| `feat` | New observable behavior (new feature, new endpoint, new component visible to users / consumers) |
| `fix` | Bug fix. Composes with `systematic-debugging` (the why = the root cause) |
| `refactor` | Structural change without behavior change. Composes with `refactoring` (named Fowler move) |
| `test` | Add / modify tests without changing production code. Includes `test: reproduce <bug>` from `systematic-debugging` |
| `docs` | Documentation only |
| `chore` | Repo maintenance (config, scripts, tooling) without user-visible effect |
| `build` | Build system / dependencies |
| `ci` | CI configuration / workflows |
| `perf` | Performance improvement with measurement |
| `style` | Formatting only (Biome auto-fix, etc.) |
No invented types (`improve:`, `tweak:`, `cleanup:`). Reach for one of the above or split the commit.
### Subject rules
- Im