1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| skill-delete | Remove a skill from the jsc skill set safely. List skills, let the user pick, inventory every file referencing the skill via a sub agent, fix each affected file through decision-tree questions until guideline checks pass, then delete the skill and open a PR via jsc-git pr. Use only for removal; not for renaming (use skill-update). |
skill-delete — delete a skill
Single source of guidelines: ../../references/guidelines.md.
Flow
- List every skill in the skill set: scan
jsc-*/skills/*/SKILL.md. - Let the user pick the skill to delete. Options state the impact scope: which skills reference it, and that its command stops working after deletion.
- Inventory every file related to the skill — this step MUST run as a sub agent:
grep -rfor the skill name and/jsc-{domain}:{name}across all jsc-* repositories- References in other SKILL.md files, the domain README's 「Skills 目錄」 section, the two marketplace.json files in
plugins/jscplus their synced copies in every domain repo,tools/, and thejsc-hookswiring
- For each affected file:
- Decide whether the file needs a fix to keep its current behavior after the deletion. If no fix is needed, skip the rest of this loop.
- Ask for fix details via the
jsc-ask:askdecision tree (call a replacement skill? inline the flow? drop the feature too?). Every option states its impact scope. - After fixing, check the guidelines.md audit checklist. On failure, return to step 4.2.
- Delete the skill directory
skills/{name}/, then sync the domain README and bump the version in all three manifests. - Call
jsc-git:prto open a Push Request.