logical-commits

Turn the current working tree into a series of clean, conventional commits. Auto-detect the repo's commit conventions, propose a grouping, gate every decision through AskUserQuestion, and respect whatever hooks the repo has configured.

Core principles

• Propose, then gate. You inspect the diff and propose the full split. The user approves or redirects through AskUserQuestion — never ask them to type out grouping decisions.
• Selections over typing. Use AskUserQuestion for type, scope, and approval gates. Free text is only for the commit description (and only when the user wants to edit yours).
• Conventional Commits, hooks honored. Format: type(scope): description. Never pass --no-verify, --no-gpg-sign, or -c commit.gpgsign=false.
• Adapt to the repo. Detect conventions from history. Don't assume a fixed scope list or a particular monorepo layout — let the data tell you.
• Honest cohesion. If the change is genuinely one thing, make one commit and say so. Don't fabricate splits.
• One commit at a time. Stage → commit → verify, group by group. If a commit fails a hook, stop and ask before continuing.

Workflow

Step 1 — Preflight

Run these checks. Abort with a clear message if any fail.