Git protocol with intelligent commit format
🚨 CRITICAL: You MUST create a commit when session work completes. NO EXCEPTIONS.
completed)WHEN (All Tasks marked completed via TaskList check) THEN {
0. Detect: Use TaskList to verify all tasks have status "completed"
1. Analyze changes for the session
2. Generate commit message referencing session
3. Execute commit with session reference
4. Report completion to user
5. Prepare session for archival
}
git diff --cached --name-onlyFormat: {type}: {summary} - Session [number] completed 🤖
Types: feat, fix, refactor, docs, style, test, build, chore
Examples:
feat: implement user profile system - Session 001 completed 🤖fix: resolve authentication flow issues - Session 002 completed 🤖refactor: optimize database connection pooling - Session 003 completed 🤖When changes span multiple logical areas:
# Example: Frontend + Backend + Database changes
git add src/components/* && git commit -m "feat: profile UI components - Auto-commit (1/3) 🤖"
git add src/server/* && git commit -m "feat: profile API endpoints - Auto-commit (2/3) 🤖"
git add supabase/* && git commit -m "feat: profile database schema - Auto-commit (3/3) 🤖"
git status - understand all changesnpm run lint && npm run typecheck (if available)Failure to auto-commit when session completes = CRITICAL FAILURE. This is MANDATORY, not optional. No exceptions.
git clean -fdxmain: Production (never direct push)dev: Development/stagingfeature/descriptiondeveloper/featureThis protocol ensures intelligent, safe, and mandatory version control.