23 lines
1.7 KiB
Markdown
23 lines
1.7 KiB
Markdown
---
|
|
name: skill-delete
|
|
description: 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`](../../references/guidelines.md).
|
|
|
|
## Flow
|
|
|
|
1. List every skill in the skill set: scan `jsc-*/skills/*/SKILL.md`.
|
|
2. 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.
|
|
3. Inventory every file related to the skill — this step MUST run as a sub agent:
|
|
- `grep -r` for 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/jsc` plus their synced copies in every domain repo, `tools/`, and the `jsc-hooks` wiring
|
|
4. For each affected file:
|
|
1. 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**.
|
|
2. Ask for fix details via the `jsc-ask:ask` decision tree (call a replacement skill? inline the flow? drop the feature too?). Every option states its impact scope.
|
|
3. After fixing, check the guidelines.md audit checklist. On failure, return to step 4.2.
|
|
5. Delete the skill directory `skills/{name}/`, then sync the domain README and bump the version in all three manifests.
|
|
6. Call `jsc-git:pr` to open a Push Request.
|