commit

Triggered by /commit. The user may provide no additional context, or a single sentence of intent — treat it as a hint, not a substitute for analysis.

Execute the steps below in order. Do not skip or reorder them.

Ground Rules

1. Gather first, decide second, act last. Never run git commit before you understand what has changed and why.
2. No ad-hoc multi-commit. If the changes need to be split into multiple commits, produce a complete plan first (see Step 4), get explicit user approval, then execute in order. Do not make it up as you go.
3. Never use --no-verify by default. Only use it if the user explicitly asks to bypass hooks in this conversation.
4. Match the repo's conventions. Infer commit message style and language from the repo's history and any contribution guidelines. Fall back to Conventional Commits in English (e.g. feat(scope): subject) only when the repo gives no clear signal.

Step 1 — Gather Information