wise-commit

# /wise-commit — draft a Conventional-Commits subject and commit Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. ## Why this skill exists `/wise-commit-message` is read-only on purpose: it drafts a subject and hands it back, so the user can review, tweak, or reject the prose before any commit object exists. That's the right shape when the operator is sitting at the keyboard. `/wise-commit` is the right shape when the operator already trusts the drafter to pick the type, scope, and prose — they want one call that stages tracked modifications, drafts the subject, and commits. No clipboard round-trip, no second invocation. The skill is a thin wrapper: read the shared [`commit-routine.md`](./commit-routine.md), set `PUSH=no` and `SIMPLIFY=yes`, and follow it. The routine is the source of truth for staging discipline, the §2 pre-staging simplify pass, Jira detection, type classification, and the final-line emit format. Pushing is `/wise-commit-push`'s job; the per-caller `SIMPLIFY` default policy lives in the routine's §"Inputs the caller sets". ## Invocation ``` /wise-commit /wise:wise-commit # canonical namespaced form ``` No positionals, no flags. If the argument string contains anything other than optional whitespa...