git-workflow-enforcer

<quick_start> <auto_commit_workflow> Automatic commit generation when changes detected:

1. Detect uncommitted changes: Run git status --porcelain
2. Classify change type: Phase completion, task completion, or file modification
3. Generate commit message: Use Conventional Commits format based on context
4. Validate safety: Check branch, merge conflicts, commit message format
5. Execute commit: Stage files and commit with generated message
6. Provide feedback: Show commit hash and rollback command

Example:

Context: Task T001 completed

❌ UNCOMMITTED CHANGES DETECTED
  Modified: api/models/message.py
  Created: api/tests/test_message.py

✅ AUTO-COMMITTING with generated message:
  feat(green): T001 implement Message model to pass test

  Implementation: SQLAlchemy model with validation
  Tests: 26/26 passing
  Coverage: 93% (+1%)

✅ COMMITTED: abc123f
  Rollback: git revert abc123f

</auto_commit_workflow>

<trigger_patterns> Auto-invoke when detecting:

Phase completion markers:

• "Phase N complete"
• "/specify complete", "/plan complete", "/tasks complete"
• "analysis complete", "optimization complete"
• Phase command finishing

Task completion markers:

• "T### complete", "task ### done"
• "task-tracker mark-done" command
• "mark task complete"

Change detection:

• git status --porcelain returns non-empty
• Files created/modified/deleted
• Working tree dirty before phase transition </trigger_patterns>

<commit_message_generation> Conventional Commits format:

<type>(<scope>): <subject>

[optional body]

[optional footer]

Auto-detection logic:

Context	Type	Scope	Subject Template
Phase 0	docs	spec	create specification for {feature}
Phase 0.5	docs	clarify	resolve {n} clarifications for {feature}
Phase 1	docs	plan	create implementation plan for {feature}
Phase 2	docs	tasks	create task breakdown for {feature} ({n} tasks)
Phase 3	docs	analyze	create cross-artifact analysis for {feature}
Phase 4 (RED)	test	red	{taskId} write failing test for {description}
Phase 4 (GREEN)	feat	green	{taskId} implement {description} to pass test
Phase 4 (REFACTOR)	refactor	-	{taskId} improve {description}
Phase 5	docs	optimize	complete optimization review for {feature}
Phase 6	docs	preview	create release notes for {feature} v{version}

Body generation:

• Phase commits: Include metrics (task count, criteria count, etc.)
• Task commits: Include evidence (tests, coverage, commit hash)
• Fix commits: Include root cause and solution

See references/commit-templates.md for complete templates. </commit_message_generation> </quick_start>

Check for uncommitted changes when:

• Phase command completes
• task-tracker mark-done-with-notes called
• User mentions "commit", "save progress", etc.

# Check for uncommitted changes
git status --porcelain

# If non-empty output → uncommitted changes exist

</detection_phase>

<classification_phase> 2. Classify Change Type and Extract Context

Phase completion:

• Extract phase name from workflow state or command
• Extract feature slug from current directory
• Get artifact file paths (spec.md, plan.md, etc.)

Task completion:

• Extract TaskId from task-tracker parameters or conversation
• Extract task description from tasks.md
• Get phase marker ([RED], [GREEN], [REFACTOR])
• Extract evidence (tests, coverage) from completion context

File modification:

• Analyze changed files to infer purpose
• Check git log for recent commit patterns
• Default to "chore" type if unclear </classification_phase>