add-commitlisted

# add-commit — Smart Commit <!-- uses: - mention: /add.done - mention: /add.pull-request - script: converge-gates.sh --> ## When to Use - Mid-workflow commits during feature development - Saving progress checkpoints before risky changes - Any `git commit` with automatic message generation - Quick commits with optional `--push` in one step ## When NOT to Use - **Finalizing a branch** → use `/add.done` instead - **Creating or updating a PR** → use `/add.pull-request` - **Force push, rebase, or amend** → out of scope - **Specific file staging** → stage manually first, then use the command --- ## Adaptive Message Logic The message format adapts to changeset size: **≤ 3 files changed** — single-line message: ``` type(scope): objective description in present tense ``` **> 3 files changed** — list format: ``` type: general summary - context/module: what changed - context/module: what changed - context/module: what changed ``` --- ## Conventional Commits Type Detection Infer the type from the diff content: | Type | When to use | |------|-------------| | `feat` | New feature, new functionality | | `fix` | Bug fix, error correction | | `refactor` | Code restructure without behavior change | | `chore` | Config, deps, scripts, tooling | | `docs` | Documentation only | | `test` | Test files only | | `style` | Formatting, whitespace, lint fixes | When ambiguous, show the inferred type and ask the user to confirm. --- ## Staging Rules Feature docs live **untracked** until