Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    big ball of mud audit

    1

    Detect architectural decay and technical debt with a scored health report and a staged refactoring plan.

    Free

    Security scanned
    big ball of mud audit

    big ball of mud audit

    Example session with this skill installed

    Audit this Next.js repo for architecture smells and tell me if I should rewrite the dashboard logic. It feels like spaghetti.

    • Read your context and instructions
    • Compiled the big ball

    I have audited the directory structure, import patterns, and business logic placement. The system shows significant coupling between the UI layer and data persistence.

    Architecture Health Score: 3/10 — Critical Big Ball of Mud risk

    Overall Assessment
    The project has reached a state where feature development is high-risk. Business logic is scattered across 14 different files rather than centralized, and the "God component" in the dashboard manages everything from raw SQL queries to chart rendering.

    Big Ball of Mud Symptoms

    • src/components/Dashboard.tsx (842 lines): Handles auth checks, Prisma calls, and D3 rendering.
    • src/pages/api/update.ts: Directly modifies the schema without validation logic, bypasses existing helpers.
    • src/utils/all.ts: 1,200-line "junk drawer" containing both UI formatting and database connection strings.

    Highest-Risk Areas

    • Data Coupling: The UI components import prisma directly. Changing the schema requires updating 12 UI files.
    • State Sprawl: Redux, React Context, and local useState are used simultaneously to track the same user object.

    Quick Wins

    • Move the 4 Prisma queries from Dashboard.tsx into a new src/services/dashboardService.ts.
    • Rename utils/all.ts to utils/formatting.ts and delete unused exports to reduce the import surface.

    Is a Full Rewrite Needed?
    No. The core logic is sound but poorly placed. An incremental "extract and delegate" approach will stabilize the system in 2 weeks without the downtime of a rewrite.

    Prioritized Action List

    • Critical — Extract DB logic from src/components/Dashboard.tsx.
    • High — Standardize API response shapes in /pages/api.
    • Medium — Consolidate user state into a single Context provider.

    Next steps

    1. Review src/services/dashboardService.ts to confirm the new boundaries.
    2. Run the provided grep commands to find the remaining 8 direct Prisma imports in the UI.
    3. Schedule a 2-day sprint to clear the "Critical" priority items.

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

    About this skill

    This skill audits codebases to detect structural decay, unplanned growth, and eroded architectural boundaries. It identifies "Big Ball of Mud" symptoms where modules are tightly coupled and temporary hacks have become permanent infrastructure. Instead of generic advice, it delivers a scored health report (0 to 10) backed by file-level evidence and a prioritized, non-destructive refactoring plan.

    What it does

    • Architectural mapping — Analyzes directory trees, dependency manifests, and import chains to visualize the system shape.
    • Complexity auditing — Locates "God files" and over-responsible components by scanning for line counts and responsibility sprawl.
    • Coupling detection — Identifies business logic leaks where UI components perform direct database queries or API calls.
    • Technical debt discovery — Greps for calcified hacks, duplicated logic, and inconsistent role-based access enforcement.
    • Refactor planning — Generates a staged, incremental action plan designed to improve architecture without breaking the live system.

    How it works

    1. Provide access to your codebase or upload specific directories for analysis.
    2. The agent maps the project structure and identifies high-risk files and coupling patterns.
    3. It evaluates the code against ten diagnostic questions regarding isolation, sustainability, and blast radius.
    4. You receive a structured report with a 0 to 10 health score and a prioritized list of refactoring tasks.

    Frameworks & tools

    Works with any language or framework. It uses standard CLI tools like grep, find, wc, and sort to analyze file structures and content.

    Why this beats prompting it yourself

    Standard prompts give vague advice like "separate your concerns." This skill forces the AI to provide specific line-item evidence, naming the exact files and symbols that violate architectural boundaries. It focuses on the "strangler-fig" pattern to ensure refactors are safe and incremental.

    Use cases

    • Deciding whether a legacy codebase needs a full rewrite or incremental refactoring.
    • Auditing a project after a period of rapid feature growth to stabilize the architecture.
    • Performing a deep-dive technical due diligence on a new repository or acquisition.
    • Identifying the highest-risk modules before starting a major system migration.

    Known limitations

    Large monorepos may require targeted scans of specific sub-directories to avoid token limits. Findings are limited to the files and directories provided in the current context.

    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.

    Requires visibility into file contents and directory structure. Large-scale audits may be limited by context window sizes. Results are scoped to provided files.

    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

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 14 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Network Access
    Listed14 days ago

    What's inside

    Frequently Asked Questions

    The skill generates a scored health report (0-10) with file-level evidence of architectural decay and a prioritized, staged refactoring plan designed to improve the system without breaking live features.

    Yes, this skill is language-agnostic; it uses structural analysis and pattern recognition via standard CLI tools to identify coupling and complexity in any codebase or framework.

    Unlike generic prompts, this skill provides line-item evidence naming exact files and symbols, and it focuses on the 'strangler-fig' pattern to ensure refactors are safe and incremental.

    Due to context window constraints, it is recommended to scan specific high-risk sub-directories or modules rather than an entire massive monorepo at once.

    No deep integration is required; you simply provide the agent access to your codebase or upload the relevant directories to initiate the automated mapping and diagnostic process.

    New in Code Quality & Review

    Free