Repository navigation
fix(cli): fold and suggest near-miss kind names - #883
Conversation
`--kind` and spec `kind` now resolve case and `-`/`_` aliases (`skill-library` → `skill_library`) the same way algorithm and parameter names already do, and a close typo ends with "did you mean 'skill_library'?". Closes #882
|
Verdict: PASS Correctness. Risk. T2 by size (package CLI/spec validation, under the 250-line cap). No evolve-loop or installer change. AGENT_PAUSE=false; will squash-merge when required CI is green (or arm |
|
Verdict: PASS
The shared helper is wired through the surfaces #882 named: One non-blocking note: Risk: T2 (under the 250-line cap). AGENT_PAUSE=false. |
Closes #882
What changed
--kindand speckindnow behave like algorithm and parameter names: a value that matches exactly one oftext,skill_dir,skill_library,agent_dir,agent_code,plugin,policy_slotonce case and-/_are ignored resolves to it (skill-library→skill_library,SKILL_DIR→skill_dir). A remaining close typo appends; did you mean 'skill_library'?. Unrelated names likenopestill get the full list and no guess.algorithms list/run,init, MCPlist_algorithms/algorithm_spec, andcomposeshareresolve_kind. Written specs use the canonical name.Verification at the tip
Tip SHA: ef39c17
Ran:
Not run: