More screenshots
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsDead-Code Deletion Safety Auditor
Prove hidden runtime reachability before removing unused code.
$19.99
Dead-Code Deletion Safety Auditor
Example session with this skill installed
Audit deletion of legacy_export_handler. Repository import search returns zero results. The route registry contains a string entry named legacy_export_handler. Scheduler manifests show no matching job. Request telemetry shows zero invocations in the last 30 days, but the business team may run quarterly export workflows. Generator inputs, stored report templates, dependency-injection string keys, and operator runbooks were not supplied. Design a safe deletion proof.
- Read your context and instructions
- Compiled the dead-code deletion safety
- Generated the document
Verdict — QUARANTINE-FIRST
The handler is still reachable through a string route, and several dynamic, generated, data, and operational paths are unbounded. Thirty quiet days cannot clear a workflow whose possible cadence is quarterly.
Deletion unit
Candidate: legacy_export_handler, including its route registration, response schema, generated client operation, templates that name its export type, tests, monitoring, and release artifact.
Reachability matrix
| Domain | Status | Evidence |
|---|---|---|
| Static | not found | repository symbol/import search |
| Reflection/DI | unknown | string-key inventory absent |
| Configuration | not found | supplied production config search |
| Plugins | not applicable | no plugin system supplied |
| Routes | reachable | route registry string entry |
| Jobs | not found | scheduler manifest search |
| Generated code | unknown | generator inputs unavailable |
| Stored data | unknown | report templates not searched |
| Tests | reachable | contract fixture imports the response schema |
| Telemetry | not found | zero requests in 30 days |
| Operations | unknown | runbook inventory absent |
Why static evidence is insufficient
The observed route registration is a direct runtime entry point even though no normal import references the handler. The telemetry interval is also shorter than the suspected reporting cadence. “Not found” therefore describes limited search results; it does not prove absence.
Safe deletion sequence
- Inventory route strings, DI keys, generator sources, stored templates, and runbooks.
- Add a bounded invocation counter at the route boundary.
- Disable the route behind a reversible guard while retaining the release artifact.
- Observe across at least one confirmed reporting cycle.
- Replay stored templates and generated-client fixtures.
- Remove code, route, generated artifacts, tests, docs, and telemetry together.
- Prove rollback by restoring the signed release artifact and route registration.
Validator
The demonstration contains all eleven reachability domains and a non-empty rollback plan and passes the bundled structural validator. No source file, route, telemetry setting, or deployment was changed.
dead-code-deletion-safety-auditor.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
Zero imports do not mean zero callers
Static search can miss reflection, dependency injection, configuration strings, plugins, routes, scheduled jobs, generated clients, stored data, templates, tests, telemetry, and operator runbooks.
Dead-Code Deletion Safety Auditor defines the proposed deletion unit, traces eleven reachability domains, records exactly what was searched, separates “not found” from “not applicable” and “unknown,” and designs a reversible instrument-disable-observe-delete sequence tied to the real invocation cadence.
Built for maintainers of mature services, monoliths, plugin systems, scheduled workloads, and generated APIs. It profiles the project's real autoloading, reflection, dependency injection, route/job registries, generators, build artifacts, tests, and release cadence.
The package includes the complete Skill source, reachability taxonomy, worked legacy-handler report, deterministic validator, mutation tests, and a six-page Buyer Guide PDF.
Boundaries
It never deletes files, edits code, commits, pushes, or deploys. Structural validation cannot prove semantic non-use or runtime unreachability.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 1 month ago
- Passed all security checks, Safe to install