silver-remove

Remove tracked work items by ID from GitHub issues and local SB trackers.

6|3|Updated Mar 31, 2026

Search Tags:#workflow #validation #docs #remove #issue-management #github-issues #tracked-item

Ready to run

npx skills add https://github.com/alo-exp/silver-bullet --skill silver-remove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: silver-remove
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-remove
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes tracked work items by ID, closing GitHub issues or marking local SB entries as removed, ensuring a clean, auditable project state.

Core Features & Use Cases

Close GitHub issues by ID (issue_tracker=github) with reason "not planned" and apply the removed-by-silver-bullet label to preserve history.
Mark local SB items (SB-I-N or SB-B-N) by prepending [REMOVED YYYY-MM-DD] to their docs/ISSUES.md or docs/BACKLOG.md entries while preserving the item body.
Validate ID formats and provide safe, idempotent operations with clear failure messages.

Quick Start

Run silver-remove with a valid ID to remove the tracked item from your project.

Frequently Asked Questions about silver-remove

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I remove tracked work items from GitHub issues and local docs?▼

To remove tracked work items, you run the skill with a valid ID, which closes GitHub issues with a "not planned" reason or marks local ISSUES.md and BACKLOG.md entries with a [REMOVED YYYY-MM-DD] heading.

What ID formats are supported for closing GitHub issues in Silver Bullet projects?▼

Closing GitHub issues and marking local items supports ID formats SB-I-N, SB-B-N, #N, or N, validating each format before performing idempotent removal operations with clear failure messages.

Can I use this to mark local BACKLOG.md entries as removed without deleting the content?▼

Yes, you can mark local BACKLOG.md entries as removed by prepending [REMOVED YYYY-MM-DD] to the item heading, preserving the original body content for auditability while updating the project state.

What happens if I try to remove an invalid or already removed tracked item ID?▼

Removing invalid IDs provides clear failure messages, while removing already processed items is an idempotent operation, meaning it safely executes without duplicating actions or corrupting your project trackers.

Does closing GitHub issues with this method preserve project history?▼

Yes, closing GitHub issues preserves history by applying a "not planned" reason and attaching a removed-by-silver-bullet label, ensuring a clean and auditable project state without deleting the original issue.