commit

Staged Commit Workflow

Create logical, grouped commits from all current changes. Follow this process exactly:

Step 0: Verify CWD & Submodule State

Before analyzing changes, verify the working state:

1. pwd — confirm you are in the project root
2. git rev-parse --show-toplevel — confirm parent repo identity
3. git submodule status — check all submodule pointers

If any submodule shows a + prefix (modified pointer), note it — this must be committed after the submodule's internal commits.

Step 1: Analyze Changes

Run these commands in parallel:

• git status — see all changed/untracked files in the parent repo
• git diff --stat — see change summary for tracked files
• git diff --cached --stat — see already-staged changes
• for d in extensions/*/; do git -C "$d" status --short; done — changes in each extension submodule (business, supply-chain, system, marketing, and any private extension a maintainer has added)
• git log --oneline -5 — see recent commit style

Step 1.5: Pre-commit Safety Scan

Before creating any commits:

1. Extension file leak: Check git status output for any files under extensions/*/ staged in the parent repo. These MUST be committed inside their submodule, not the parent.
   • If found: Unstage them (git reset HEAD extensions/...) and commit inside the submodule instead
2. Ruby syntax gate: If there are staged .rb files, verify: git diff --cached --name-only -- '*.rb' | head -5 | xargs -I{} ruby -c {}
3. TypeScript gate: If there are staged .ts/.tsx files, verify: cd frontend && npx tsc --noEmit 2>&1 | tail -5

Step 2: Group Files by Concern

Organize changed files into groups (skip empty groups):

1. Migrations — db/migrate/
2. Models — app/models/
3. Services — app/services/
4. Controllers & Routes — app/controllers/, config/routes.rb
5. Frontend — frontend/src/
6. Tests — spec/, e2e/, __tests__/
7. Seeds & Config — db/seeds/, config/, .claude/, scripts/
8. Documentation — docs/, *.md (only if explicitly changed)