commit-smart

Topics in the source

• Smart Commit
• Workflow
• Step 1: Assess the working tree
• Step 2: Handle unstaged changes
• Step 3: Analyze the diff
• Step 4: Check for user overrides
• Step 5: Compose the commit message
• Step 6: Confirm and commit

Create meaningful conventional commits by analyzing your actual changes. Run these commands to understand the current state: If nothing is staged (git diff --cached is empty): 1. Show the user what files have changed 2. Suggest what to stage based on logical grouping (e.g., "these 3 files are all related to the auth refactor") 3. Ask if they want to stage all, or select specific files 4. Stage the approved files with git add If changes are already staged, proceed to analysis. Read the full staged diff: Determine the commit type from the changes: | Signal | Type | |--------|------| | New files with new functionality | feat | | New test files or test additions | test | | Changes to existing logic fixing incorrect behavior | fix | | Structural changes without behavior change | refactor | | package.json, tsconfig, CI config changes | chore | | Build/bundler config changes | build | | README, docs, comments only | docs | | Formatting, whitespace, semicolons only | style | | Performance improvements | perf | Determine the scope from the primary directory or module affected: src/api/ -> api src/components/auth/ -> auth tests/ -> tests Root config files -> omit scope Multiple unrelated are

This is an excerpt. Refer to the complete source and its current requirements.