More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    tech debt architect

    2

    Architectural auditor that transforms code smells and Git history into a prioritized, business-case refactoring roadmap.

    $7.77

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    tech debt architect

    tech debt architect

    Example session with this skill installed

    Scan this repo for tech debt. We have a release in two days so I can only fix critical issues. The payment module is a frozen zone.

    • Read your context and instructions
    • Compiled the tech debt architect

    Tech Debt Score: C Dangerous
    Total estimated remediation: 12 person-days
    Failure-rate increase: 15% in 3 months

    P0 | Blocking | src/auth.js:42-45 | Hardcoded API Key | Git: hotfix-09-12 | Use Env Var | 1h | High

    Phase 1: Stop the bleeding. Fixing P0 auth leak and P1 cyclic dependency in billing.

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

    About this skill

    The problem

    Legacy codebases often suffer from hidden coupling traps, security vulnerabilities, and performance bottlenecks that slow down feature delivery. Developers struggle to justify refactoring time to stakeholders who only care about business value and deadlines.

    What it does

    • Performs a multi-dimensional scan for code smells, architectural defects, security risks, and performance bottlenecks.
    • Maps every identified debt to specific files, function names, and exact line ranges.
    • Analyzes Git history to identify root causes like deadline rushes or multi-author collisions.
    • Generates a prioritized P0 to P3 inventory with estimated remediation effort in person-days.
    • Produces a dependency-aware refactoring roadmap with a phased execution plan.

    Frameworks & tools

    Works across any language. Utilizes Git, Glob, and Grep for deep repository analysis and history auditing.

    Why this beats prompting it yourself

    Generic prompts result in vague advice like "improve cohesion." This skill enforces a rigorous four-part architectural audit, requires concrete before/after code snippets for every recommendation, and uses Git forensics to prove why code is failing, making the business case for you.

    Use cases

    • Audit a new repository to assess maintainability and release risks.
    • Create a phased refactoring roadmap that respects business-critical frozen zones.
    • Identify high-risk security flaws like SQL injection or hardcoded secrets.
    • Estimate the man-hours required to stabilize a fragile legacy module.

    Known limitations

    Requires access to source files for line-level accuracy. Git-based root cause analysis is unavailable for zip-file uploads or repos without history.

    Requires local source code access for line-number accuracy. Git forensics are unavailable for repositories without a .git history.

    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 3 months ago

    Permissions

    Environment Variables
    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill performs deep repository forensics by combining static code analysis with Git history to identify not just where the code is messy, but which files are causing the most churn and technical drag on your team.

    It is language-agnostic and functions across any codebase where Git, Glob, and Grep can be executed, making it equally effective for monolithic Java apps or modern TypeScript microservices.

    Every reported issue includes a severity rating (P0-P3), an estimated remediation time in person-days, and a clear business justification to help you secure stakeholder approval for refactoring.

    The skill requires access to your source files and Git history metadata; please note that analyzing a flat ZIP file without history will disable the 'root cause' and 'churn analysis' features.

    You receive the full architectural audit logic, pre-configured workflows for phased refactoring plans, and periodic updates to the detection patterns for new security vulnerabilities and code smells.

    New in Code Quality & Review