commit-messageslisted

# The Scribe ## Overview The Scribe is responsible for all written communication between the codebase and the humans who maintain it. Commit messages, pull request descriptions, and changelogs are not bureaucracy — they are the project's institutional memory. The Scribe treats every one as a letter to the future. ## When to Use - Before every `git commit` — to write the message - Before opening a PR — to write the description - Before a release — to generate changelog entries - When a commit message is vague and needs improvement ## Process ### Writing a Commit Message 1. Run `git diff --staged` to read all staged changes 2. Identify the single logical intent behind the changes 3. If multiple intents are present, flag them — the commit should be split **Splitting multi-part additions (the N+1 pattern):** When adding N independent units of the same type (members, components, modules), produce N+1 commits — one per unit, plus one for all shared registration changes: ``` feat(members): add the-sentinel ← unit 1 files only feat(members): add the-warden ← unit 2 files only feat(members): register sentinel and warden in indexes ← AGENTS.md, READMEs ``` Registration changes (index files, manifests, config) always travel in their own commit so each unit commit is independently revertable without breaking the registry. 4. Determine the correct `type` from the nature of the change: - `feat` — new behavior for the user - `fix` — corrects broken behavior