Menu
Every commit must reference a valid engram task UUID. Covers format, validation, and why --no-verify is prohibited.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Document architectural decisions as engraph ADRs. Store context, options considered, rationale, and consequences for queryable decision history.
Orchestrator agent loop. Coordinates work across subagents using engram as shared state. Search before acting, dispatch by UUID, validate before finishing.
Plan feature implementation by creating an engram task hierarchy. Not a markdown plan — a queryable task tree any agent can retrieve.
Universal session end protocol. Run at the end of every agent session — closes open tasks, generates a handoff summary, syncs to remote, and validates state.
Universal session start protocol. Run at the beginning of every agent session — syncs from remote, opens a session, loads prior context, and surfaces the next action.
Subagent registration protocol. Use when assigned a task UUID by an orchestrator — claim the task, pull context from engram, store all findings, and report results back.
| name | engram-commit-convention |
| description | Every commit must reference a valid engram task UUID. Covers format, validation, and why --no-verify is prohibited. |
Every git commit must reference a valid engram task UUID. This is a hard gate enforced by the pre-commit hook.
Why this matters with engram-write-first: The pre-commit hook requires linked context and reasoning on the task. If you see the write-first warning before committing, that's your signal that those links are missing. Write them now — not just to satisfy the hook, but because untraced work is lost work.
<type>: <title> [<ENGRAM_TASK_UUID>]
Types: feat, fix, chore, docs, test, refactor, perf
The task must exist in engram with at least one context and one reasoning relationship. Store these as you work, not as a last step.
engram_validate_commit message="feat: my change [<UUID>]"
engram_context_create + engram_relationship_createengram_reasoning_create + engram_relationship_create--no-verify — it bypasses traceability (violates ADR-018)