More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dead-Code Deletion Safety Auditor

    1

    Prove hidden runtime reachability before removing unused code.

    $19.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dead-Code Deletion Safety Auditor

    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

    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

    DomainStatusEvidence
    Staticnot foundrepository symbol/import search
    Reflection/DIunknownstring-key inventory absent
    Configurationnot foundsupplied production config search
    Pluginsnot applicableno plugin system supplied
    Routesreachableroute registry string entry
    Jobsnot foundscheduler manifest search
    Generated codeunknowngenerator inputs unavailable
    Stored dataunknownreport templates not searched
    Testsreachablecontract fixture imports the response schema
    Telemetrynot foundzero requests in 30 days
    Operationsunknownrunbook 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

    1. Inventory route strings, DI keys, generator sources, stored templates, and runbooks.
    2. Add a bounded invocation counter at the route boundary.
    3. Disable the route behind a reversible guard while retaining the release artifact.
    4. Observe across at least one confirmed reporting cycle.
    5. Replay stored templates and generated-client fixtures.
    6. Remove code, route, generated artifacts, tests, docs, and telemetry together.
    7. 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.

    Connects securely to your tools. The creator never sees your data.

    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.

    Requires buyer-supplied code or search evidence, route and job registries, configuration, telemetry summaries, or tests. It never deletes files, edits code, commits, pushes, or deploys. Structural validation cannot prove semantic non-use or runtime unreachability.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    While static analysis tools identify unreferenced code, this skill goes further by auditing dynamic reachability domains—like reflection, dependency injection, and scheduled jobs—to ensure code that appears 'dead' isn't actually being called at runtime.

    No, the skill is strictly an auditing and validation tool; it generates a safety report and a reversible decommission plan, but it never modifies, deletes, or commits code to your repository.

    The purchase includes the full Skill source code, a comprehensive reachability taxonomy, a deterministic validator, mutation tests, and a six-page Buyer Guide to help you integrate it into your workflow.

    The auditor is designed to profile mature services, monoliths, and plugin-based architectures where complex routing and autoloading make traditional dead-code detection unreliable.

    The skill defines a custom 'instrument-disable-observe-delete' sequence based on your specific release cadence to ensure that no code is removed until its lack of usage is proven over a real-world timeframe.

    New in Code Quality & Review