fix(model-routing): keep commit grouping on the sonnet subagent (edit<n> re-dispatches; /feat routes to /commit-change)

This commit is contained in:
Bastien Chanot
2026-07-15 21:24:48 +02:00
parent ab0fafc0ef
commit 4217fcfe35
2 changed files with 8 additions and 5 deletions
+4 -3
View File
@@ -75,9 +75,10 @@ AskUserQuestion:
- `all` → every step in the plan is approved as-is. - `all` → every step in the plan is approved as-is.
- `<numbers>` (e.g. `1,3`) → only those steps are approved; the rest stay - `<numbers>` (e.g. `1,3`) → only those steps are approved; the rest stay
uncommitted for a later run. uncommitted for a later run.
- `edit <n>` → collect the corrected message/grouping for step N from the - `edit <n>` → re-dispatch `commit-changer` with `MODE: propose` and the
user, redraw the plan (this dispatcher owns the text, no re-dispatch user's correction for step N folded into the prompt, so all grouping /
needed), show it again and re-ask. message judgment stays on the sonnet subagent (never redrawn inline on
the session model); show the redrawn plan and re-ask.
- `skip` → exit cleanly, no commits created, no `MODE: apply` dispatch. - `skip` → exit cleanly, no commits created, no `MODE: apply` dispatch.
## STEP 3 — Gate 2: capitalize approval ## STEP 3 — Gate 2: capitalize approval
+4 -2
View File
@@ -173,8 +173,10 @@ feat(<scope>): <what was added>
``` ```
If the feature touched multiple concerns (e.g., feature + config + If the feature touched multiple concerns (e.g., feature + config +
test), consider splitting into 2-3 atomic commits — load test), consider splitting into 2-3 atomic commits grouped by logical
`$HOME/.claude/agents/commit-changer.md` and follow its grouping logic. unit — or run `/commit-change` on the pending work (it dispatches the
sonnet commit-changer; never inline-load the bare agent, it is now a
propose/apply executor).
Print summary: Print summary:
``` ```