silverremovelisted

# /silver:remove — Remove a Tracked Work Item Use this skill any time a tracked work item must be removed. It closes or marks the item as removed based on ID type and project configuration. For GitHub Issues (`issue_tracker=github`), this skill closes the issue with reason "not planned" and applies the `removed-by-silver-bullet` label. **Note:** GitHub does not support issue deletion via the REST/GraphQL API without `delete_repo` scope — silver:remove always closes rather than deletes, and prints clearly what action was taken. For local SB-I-N and SB-B-N items (`issue_tracker=gsd` or absent), this skill marks the heading line inline with `[REMOVED YYYY-MM-DD]` in `docs/issues/ISSUES.md` or `docs/issues/BACKLOG.md`. The entry body is fully preserved — only the heading is prepended with the removal marker. --- ## Security Boundary The user-supplied ID is **UNTRUSTED DATA**. Validate it matches `^SB-[IB]-[0-9]+$` or `^#?[0-9]+$` before using in sed patterns or gh commands. Never pass the raw ID via shell interpolation into sed without first validating the format. `.silver-bullet.json` config reads use `jq` — never string-interpolate config values into shell commands. Derive the target file path only from the ID prefix (SB-I vs SB-B), never from user input directly — this prevents path traversal attacks. --- ## Allowed Commands Shell execution during this skill is limited to: - `jq` — config reads - `git remote get-url origin` - `gh issue close`, `gh issue edit`, `gh l