Export Cleanup Auditor

    1

    Backup hygiene audits: find stale exports, orphaned files, and shrink your storage footprint.

    Secure checkout via Stripe

    0 installsSecurity scanned

    Works with the AI tools you already use

    CClaude CodeCCursorCCodex CLIGGitHub CopilotGGemini CLIVVS CodeWWindsurfMManus+14 more

    See it in action

    You say

    Audit the exports in the /src directory of this TypeScript library and prepare a cleanup plan for the v2.0 release.

    Your agent does

    # Export Audit — @ui/core | Name | Kind | Refs | Status | Action | | :--- | :--- | :--- | :--- | :--- | | legacyFormat | Function | 0 | Dead | Delete | | internalUtility | Const | 12 | Internal-only | Move to /internal | - [ ] Build passes after removing legacyFormat.

    What you get

    Identify dead exports with zero references for safe deletion.Find internal utilities that should be hidden from the public API.Prepare for major version bumps by flagging deprecation candidates.Audit undocumented public functions that require documentation or removal.

    About this skill

    The problem

    Public API surfaces grow organically until you no longer know what is safe to delete. Stale exports and orphaned modules bloat your package size and increase the maintenance burden of your next major version.

    What it does

    • Identifies the package boundary using package.json, pyproject.toml, or go.mod.
    • Scans the entire repository using ripgrep to map internal versus external usage of every export.
    • Categorizes code into Dead, Internal-only, Public & used, or Public but undocumented.
    • Generates a structured cleanup plan with risk assessments for SemVer compliance.
    • Verifies that deletions won't break the build or existing test suites.

    Why this beats prompting it yourself

    Manual grepping is error-prone and misses edge cases like string-based dynamic imports or type-only references. This skill automates the cross-referencing logic and applies a systematic risk-grading framework that ensures you don't accidentally ship a breaking change in a minor release.

    Use cases

    • Pre-release audits to slim down a library before a major SemVer bump.
    • Identifying "internal-only" utilities that were accidentally exposed to the public API.
    • Finding dead code left over from refactors that eslint or pyright missed.
    • Mapping undocumented public functions that need tests or deprecation notices.

    Known limitations

    Not for performance profiling or style linting. Best results require running on a clean branch without work-in-progress code.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    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 today

    Listedtoday

    Frequently Asked Questions