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

skills/commit-change/SKILL.md

@@ -75,9 +75,10 @@ AskUserQuestion:
 - `all` → every step in the plan is approved as-is.
 - `<numbers>` (e.g. `1,3`) → only those steps are approved; the rest stay
   uncommitted for a later run.
-- `edit <n>` → collect the corrected message/grouping for step N from the
-  user, redraw the plan (this dispatcher owns the text, no re-dispatch
-  needed), show it again and re-ask.
+- `edit <n>` → re-dispatch `commit-changer` with `MODE: propose` and the
+  user's correction for step N folded into the prompt, so all grouping /
+  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.
 
 ## STEP 3 — Gate 2: capitalize approval

skills/feat/SKILL.md

@@ -173,8 +173,10 @@ feat(<scope>): <what was added>
 ```
 
 If the feature touched multiple concerns (e.g., feature + config +
-test), consider splitting into 2-3 atomic commits — load
-`$HOME/.claude/agents/commit-changer.md` and follow its grouping logic.
+test), consider splitting into 2-3 atomic commits grouped by logical
+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:
 ```