code-deletion-cleanup

Construct and execute a controlled deletion queue with ownership and status tracking.

2|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/CrypticSwarm/Swarmforge --skill code-deletion-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-deletion-cleanup
Source: https://github.com/CrypticSwarm/Swarmforge/tree/main/opencode/config/skills/code-deletion-cleanup
Command: npx skills add https://github.com/CrypticSwarm/Swarmforge --skill code-deletion-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Code Deletion Cleanup workflow helps engineers delete code targets while thoroughly cleaning up ripple effects, preventing cascading breakages and unmanaged cruft.

Core Features & Use Cases

  • Preflight clarifications and a deletion queue with explicit ownership and statuses.
  • Dependency inventory and repo-wide checks to prevent accidental deletions of entry points or public APIs.
  • End-to-end cleanup: remove unused imports, rewire build graphs, and audit tests after deletion.
  • Use case: safely remove a deprecated feature across HTTP endpoints, CLI commands, and scheduled jobs.

Quick Start

Initiate the deletion workflow for a target and let the system manage the queue and verification.

Frequently Asked Questions about code-deletion-cleanup

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

FAQPage Schema
How do I safely delete code across a large codebase without breaking the build?▼

Safely delete code by using a controlled deletion queue with explicit ownership and preflight dependency inventories. Apply repo-wide checks to prevent accidental removal of entry points or public APIs, followed by post-delete cleanup to maintain build consistency.

What is the best way to clean up ripple effects when removing deprecated features?▼

Clean up ripple effects by performing end-to-end removal of unused imports, rewiring build graphs, and auditing tests. This ensures that deleting a deprecated feature across HTTP endpoints, CLI commands, and scheduled jobs does not cause cascading breakages.

Can I track the audit trail and ownership status of code deletion targets?▼

Yes, you can track the audit trail by utilizing a deletion queue that enforces explicit ownership and status tracking. This ensures an auditable history throughout the iterative verification and rollback processes.

How do I prevent accidental deletion of public APIs and entry points?▼

Prevent accidental deletion of public APIs and entry points by running dependency inventories and repo-wide preflight checks. These checks identify critical call graphs and configurations before executing the controlled deletion queue.

Does code cleanup work for iterative verification and rollback scenarios?▼

Yes, code cleanup supports iterative verification and rollback scenarios. The deletion queue manages status tracking explicitly, allowing you to verify build consistency progressively and roll back changes if cascading breakages occur.