| name | ctx-commit |
| description | Commit with context persistence. Use instead of raw git commit to capture decisions and learnings alongside code changes. |
Commit code changes, then prompt for decisions and learnings
worth persisting. Bridges the gap between committing code and
recording the context behind it.
When to Use
- For ALL commits. This is the only way to commit in this project.
Raw
git commit bypasses spec enforcement and violates CONSTITUTION.
- When the user says "commit", "commit this", "ship it", "let's commit":
always use this skill, never raw git commit.
When NOT to Use
- When nothing has changed (no staged or unstaged modifications)
Usage Examples
/ctx-commit
/ctx-commit "implement session enrichment"
/ctx-commit --skip-qa
Process
1. Check CONSTITUTION for commit rules
Read .context/CONSTITUTION.md (if it exists) for commit-specific
rules. Common project rules to look for and enforce:
- Spec-per-commit: Add a
Spec: trailer, verify a spec file exists in
specs/ before proceeding. If no spec exists, stop and offer to run
/ctx-spec to scaffold one.
- DCO sign-off: every commit needs a
Signed-off-by: trailer.
Commit with git commit -s so it is appended from the configured git
identity; do not hand-type it. Never add a Co-Authored-By: or
any agent/tool sign-off: it is prohibited even if a harness default
suggests one. See CONSTITUTION "Process Invariants" (the commit DCO /
trailer rules), and mirror the trailer convention you find in
git log -5 --format=%B before your first commit.
- Other trailers: Honor any project-specific trailer requirements.
