| name | manifest-commit |
| description | Write knowledge-transfer git commits for Manifest projects. Use when making git commits. Commits include a typed subject line and a detailed body explaining what changed, why, and how. |
Manifest Commit
Write a git commit for the current changes. In Manifest, commits are knowledge transfer — the primary way agents and humans understand what happened and why.
Format
<type>(<scope>): <summary>
type REQUIRED. feat, fix, docs, refactor, chore, test, perf.scope OPTIONAL. The area affected: a feature name, manifest, cli, config, etc.summary REQUIRED. Imperative, <= 72 chars, no trailing period.
The Body Is Not Optional
Every commit gets a body unless it's a one-character typo fix. The body is how the next agent learns what you did. Write it for someone (or something) reading git log weeks from now with no other context.
What to include:
- What changed — which files, which behaviors, what's different now
- Why it changed — the reasoning, the problem it solves, the context that led here
- How it was done — the approach, key decisions, tradeoffs considered
- Migration notes — if this change requires other files to be updated, say so explicitly. Name the files. If the change is large, point to a plan:
See .pi/plans/2026-02-15-feature.md
- What was NOT done — if you deliberately left something out or chose not to change something related, note it so the next person doesn't wonder
