# Create Comprehensive Commit This task guides the creation of a high-quality, comprehensive commit message that accurately reflects all staged changes, adhering to Conventional Commits 1.0 standard with anti-tunnel vision mechanisms. ## Purpose Create commit messages that: - Capture ALL work streams, not just the primary change - Provide context for future developers - Follow Conventional Commits standard - Document the "why" behind changes - Prevent tunnel vision through systematic evidence gathering ## Process ### 1. Comprehensive Evidence Gathering (MANDATORY) #### 1.1 Staged Changes Analysis Execute and analyze: ```bash # Get summary and detailed view git diff --staged --stat # See operation types (Modified, Added, Deleted) git diff --staged --name-status ``` Group changes by functional area: - **Source Code**: Core application logic - **API/Backend**: Endpoints, services, repositories - **UI/Frontend**: Components, styles, templates - **Documentation**: README, docs/, *.md files - **Tests**: Test files, test utilities - **Configuration**: Config files, environment settings - **Database**: Migrations, schema changes - **Build/Deploy**: CI/CD, build scripts For each file, identify: - New functionality added - Existing functionality modified - Bug fixes - Refactoring or cleanup - Documentation updates - Test additions/modifications #### 1.2 Completeness Check ```bash # Check for unstaged/untracked files git status --porcelain ``` If related files are unstaged: - Prompt user about inclusion - Ensure completeness of the commit #### 1.3 Work Stream Identification Identify: - **Primary Work Stream**: Main focus of the commit - **Secondary Work Streams**: Supporting changes - **Cross-Functional Impact**: Changes spanning multiple areas - **Architecture Impact**: Pattern or structural changes ### 2. Multi-Context Analysis (MANDATORY) #### 2.1 Session Context Review: - Conversation history for context - Original problem/request - Key decisions made - Scope evolution (if any) #### 2.2 Development Context Check for: - Related dev journal entries - Part of larger feature/fix - Recent related commits - Project milestones #### 2.3 Business & Technical Context Understand: - User-facing benefits - Technical improvements - Problem-solution mapping - Alternatives considered ### 3. Commit Message Synthesis #### 3.1 Type and Scope Selection **Types** (choose most significant): - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation only - `style`: Formatting, no logic change - `refactor`: Code restructuring - `perf`: Performance improvement - `test`: Test additions/modifications - `chore`: Maintenance tasks **Scope** examples: - Component-specific: `api`, `ui`, `auth`, `db` - Feature-specific: `user-management`, `reporting` - System-wide: Use when changes affect multiple areas #### 3.2 Message Structure ``` ():