Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Export Cleanup Auditor

    10

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

    Free

    4 usesSecurity scanned
    Export Cleanup Auditor

    Export Cleanup Auditor

    Example session with this skill installed

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

    • Read your context and instructions
    • Compiled the export cleanup auditor

    Export Audit — @ui/core

    NameKindRefsStatusAction
    legacyFormatFunction0DeadDelete
    internalUtilityConst12Internal-onlyMove to /internal
    • Build passes after removing legacyFormat.

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

    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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Run on clean main branch. Dynamic imports via string paths create uncertainty. Does not handle performance profiling or style linting.

    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 buying a skill.

    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

    4 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    The Auditor supports a variety of ecosystems including JavaScript/TypeScript, Python, and Go by analyzing package manifest files to define library boundaries. It utilizes high-performance scanning to map exports across your entire repository.

    While standard linters find unused variables, this skill performs a holistic architectural audit to distinguish between internal usage and public API exposure. It specifically identifies 'leaked' exports that are used internally but shouldn't be accessible to end-users.

    The skill generates a structured cleanup plan that categorizes every export by risk level. This helps you determine if a deletion is a safe patch, a minor internal refactor, or a major breaking change requiring a SemVer bump.

    Once purchased, you receive the full skill package for your AI agent, including a configuration guide for various repository environments. You will also have access to any future updates or compatibility patches released for new agent versions.

    For the most accurate results, it is recommended to run the audit on a clean, stable branch. This prevents 'work-in-progress' code from creating false positives or interfering with the dependency mapping logic.

    New in Code Quality & Review

    Free