mirror of
https://github.com/codestable/CodeStable.git
synced 2026-09-19 09:03:09 +08:00
dafang
7a40410cfe
Dogfood feedback (session 001c553b): calling cs with a concrete request recommended an entry and then waited for the user to re-invoke it — one confirmation too many. cs now classifies intent: clear action requests announce the chosen entry in one line and continue executing under that skill's discipline in the same turn; advice requests still get a recommendation only; ambiguous requests that would materially change what happens next get exactly one focused question. Handoff does not widen authority — the target skill's gates and checkpoints apply unchanged. Safety anchors and docs (SKILL_CATALOG / WORKFLOW / README zh+en) synced. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
CodeStable v2 Skill Catalog
v2 ships exactly 8 skills. Each is an independent installation unit and does not depend on sibling skill files or a centralized onboard runtime.
Current Entries
| Group | Skill | Responsibility |
|---|---|---|
| Navigation | cs |
Clear action requests dispatch to the target skill in the same turn; advice gets a recommendation only; the overview writes no files |
| Onboarding | cs-onboard |
Create minimal project memory and explain a lossless v1 upgrade |
| Feature | cs-feat |
Implement new capability; scale design confirmation and independent review with risk |
| Issue | cs-issue |
Fix bugs or broken existing behavior with red-to-green evidence |
| Refactor | cs-refactor |
Change structure or performance under verifiable behavioral equivalence |
| Epic | cs-epic |
Decompose, confirm, and drive multiple deliverable items over time |
| Review | cs-code-review |
Perform independent read-only review or an on-demand module/repository audit |
| Memory | cs-keep |
Store evidence-backed frequent facts or reusable lessons in project memory |
Retired v1.0.4 Entries
The following 24 names are retired and not shipped in v2. No compatibility shims are installed. Upgrading preserves historical project artifacts; it only removes these triggers from the new skill package.
| v1 names | v2 approach |
|---|---|
cs-feat-design, cs-feat-design-review, cs-feat-impl, cs-feat-qa, cs-feat-accept, cs-feat-ff |
Use cs-feat; risk and repository facts determine execution strength |
cs-issue-report, cs-issue-analyze, cs-issue-fix |
Use cs-issue |
cs-refactor-ff |
Use cs-refactor |
cs-audit |
Use the audit mode of cs-code-review |
cs-goal, cs-roadmap, cs-roadmap-review, cs-roadmap-impl-goal |
Use cs-epic for large initiatives; ordinary cross-session work uses one work document |
cs-brainstorm, cs-domain, cs-req |
Clarify within cs-feat / cs-epic; update project docs or ADRs directly |
cs-docs, cs-docs-neat, cs-doc-api, cs-doc-tutorial |
Update docs as part of the owning development task, or request a standalone documentation edit directly |
cs-note |
Use cs-keep |
cs-feedback |
Store project lessons with cs-keep; submit product feedback through the repository issue process |
Call cs when the mapping is unclear. See
WORKFLOW.en.md for v1 project-asset preservation.