epicenter impact analysis

    1

    Map Python call graphs, find dead code, and analyze refactoring impact via an MCP-powered static analysis engine.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    epicenter impact analysis

    Example session with this skill installed

    What is the impact of refactoring the BaseProcessor.validate method in this repo? Are there any untested callers?

    • Read your context and instructions
    • Compiled the epicenter impact analysis

    I have analyzed the call graph for BaseProcessor.validate. The impact spans 3 modules, including one indirect caller that is currently untested.

    Impact Analysis: BaseProcessor.validate

    Dependent SymbolTypeDistanceFlags
    processors.UserProcessor.validateOverride1-
    api.endpoints.submit_dataDirect Call1[HIGH FAN-IN]
    tasks.background_worker.process_queueIndirect Call2[UNTESTED]
    tests.test_processors.test_base_validationTest Path1-

    Analysis Summary

    High Risk: api.endpoints.submit_data is a high fan-in node. Changes to the validation logic may trigger widespread failures in the ingestion API.

    Test Gap: tasks.background_worker.process_queue reaches this method through an indirect reference but has no associated test coverage. A regression here will not be caught by the CI suite.

    Inheritance: UserProcessor overrides this method; ensure the signature change is reflected in the subclass to avoid TypeError.

    Next steps

    1. Add a unit test in tests/test_workers.py that exercises the process_queue path.
    2. Update the signature in processors/user.py to match your intended changes.
    3. Re-run index_codebase() after the refactor to verify the new graph integrity.

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

    About this skill

    Refactoring Python code is often a guessing game of grep and hope. Epicenter eliminates the risk by providing a real call-graph analysis to see exactly what breaks before you touch a single line. It maps direct and indirect dependencies, identifies untested impact zones, and finds dead code using static analysis rather than simple text matching.

    What it does

    • Impact mapping traces direct and indirect callers across the codebase, including inherited overrides and typed variable resolutions.
    • Dependency analysis lists every symbol a specific class or function relies on to help you understand unfamiliar code blocks.
    • Coverage reachability identifies which tests actually reach a symbol, highlighting high-risk areas marked as [UNTESTED].
    • Dead code detection surfaces functions and classes that no entrypoint or test reaches, serving as candidates for safe removal.
    • Change coupling uses historical git data to find symbols that frequently change together, even if they lack a direct code path.

    How it works

    1. Initialize the index by calling index_codebase on your project root to build the initial call graph snapshot.
    2. Search for symbols using find_symbol to get the exact qualified name of the class or function you intend to modify.
    3. Analyze the blast radius by running impact_of to see every dependent symbol, ranked by distance and fan-in.
    4. Audit safety via test_coverage and dead_code to confirm if your changes are guarded by existing tests.

    Frameworks & tools

    This skill operates as an MCP server using epicenter-mcp. It is designed specifically for Python codebases and integrates with git for historical coupling analysis.

    Why this beats prompting it yourself

    Standard LLM prompts rely on the context window and basic text search, which miss indirect callers and complex inheritance. This skill uses a dedicated static analysis engine to provide a mathematically sound graph of your code, catching dependencies that grep ignores.

    Use cases

    • Safe refactoring to see every affected module before renaming a core utility function.
    • Code cleanup to identify and remove truly unreachable classes and methods.
    • Risk assessment to flag [UNTESTED] dependents that require new manual test cases.
    • Onboarding to map out the dependencies of a complex class before attempting a feature addition.

    Known limitations

    Limited to Python. Cannot resolve dynamic dispatch via getattr, string-based attribute access, or unannotated duck typing. Results reflect the last indexed snapshot, not live unsaved edits.

    Python only. Misses dynamic dispatch (getattr), unannotated indirection, and mid-function type reassignment. Requires CLI history mining for coupling data. Results depend on periodic re-indexing.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    • Free with an Agensi account

    Requires

    Epicenter MCP
    uv (Python tool runner)

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    Unlike standard LLMs that rely on text matching, Epicenter uses a dedicated static analysis engine to map Python call graphs, uncovering indirect dependencies and inheritance chains that simple prompts or grep might miss.

    Epicenter is built as an Model Context Protocol (MCP) server, making it compatible with any AI agent or IDE that supports the MCP standard, such as Claude Desktop or similar developer tools.

    The skill currently provides specialized support for Python codebases, utilizing type hints and static analysis to map symbol relationships and detect dead code.

    Setup involves installing the `epicenter-mcp` package and running an initial index command on your project root to build the call graph snapshot for the AI to query.

    The skill identifies 'dead code' by surfacing functions and classes that lack any reachable entry points or test coverage within the indexed call graph, flagging them as candidates for removal.

    Because it uses static analysis, it cannot resolve dynamic dispatch methods like `getattr()` or unannotated duck typing where the relationship isn't explicitly defined in the code structure.

    New in Code Quality & Review