dev-commitlisted

# enggenie:dev-commit **Announce:** "I'm using enggenie:dev-commit to create a commit message." ## Overview Analyze staged changes and propose a well-crafted commit message. The message explains WHY something changed, not just what changed. Every commit gets user approval before it lands. --- ## Step 1: Analyze Staged Changes Run these commands to understand what is being committed: ```bash git status git diff --staged ``` Read the full diff output. Understand: - Which files changed and why - Whether the changes are a new feature, bug fix, refactoring, documentation, test, or performance improvement - The relationship between changed files (are they part of one logical change?) If nothing is staged, tell the user: "No changes are staged. Stage your changes with `git add` first." --- ## Step 2: Propose Commit Message ### Commit Types Only use the following types: | Type | When to use | |------|------------| | `feat:` | New feature or capability | | `fix:` | Bug fix | | `refactor:` | Code restructuring without behavior change | | `docs:` | Documentation only | | `style:` | Formatting, whitespace, linting (no logic change) | | `test:` | Adding or updating tests | | `perf:` | Performance improvement | | `chore:` | Build, config, tooling, dependencies | ### Format ``` <type>: <concise_description> <optional_body_explaining_why> ``` ### Rules - **Present tense.** "add feature" not "added feature" - **Explain why, not what.** The diff shows what changed. The messa