git-commitlisted

# Git Commit Create a commit with a conventional commit message based on staged changes. Automatically stages all changes and analyzes the diff to generate an appropriate commit message. ## Workflow Execute these steps in order. --- ### Step 1: Check Repository State Check for changes to commit: ```bash git status --porcelain ``` - If output is empty, report: "Nothing to commit. Working directory is clean." and stop. - If changes exist, continue to Step 2. --- ### Step 2: Stage All Changes Stage all changes including untracked files: ```bash git add . ``` Report: "Staged all changes." --- ### Step 3: Analyze Changes View the staged diff to understand what changed: ```bash git diff --cached --stat ``` ```bash git diff --cached ``` Analyze the diff to determine: - The type of change (feat, fix, docs, refactor, etc.) - The scope (optional, based on affected files/modules) - A concise description of what changed --- ### Step 4: Construct Commit Message Build a conventional commit message following this format: ``` <type>(<optional-scope>): <description> [optional body] ``` **Types:** - `feat` - New feature - `fix` - Bug fix - `docs` - Documentation only - `style` - Formatting, no code change - `refactor` - Code restructuring without behavior change - `test` - Adding or updating tests - `chore` - Maintenance tasks - `build` - Build system or dependencies - `ci` - CI configuration - `perf` - Performance improvement **Rules:** - Use imperative mood ("add" n