2

    tech-debt-scanner

    by Zicheng Liao

    Audit your codebase for technical debt and generate a prioritized, actionable remediation report.

    Updated May 2026
    0 installs

    Free

    One-time purchase

    Included in download

    • Downloadable skill package
    • 1 permission declared
    • Instant install

    See it in action

    A real example of what this skill takes in and produces.

    Sample output

    [CRITICAL] Auth.ts: FIXME in login flow (Line 42) [HIGH] OrderService.go: Function 'ProcessPayment' is 142 lines (Max: 50) [MEDIUM] package.json: 'lodash' is 18 months out of date. Summary: 1 Critical, 4 High, 12 Medium debt items found. Recommendation: Refactor 'ProcessPayment' to improve testability.

    About This Skill

    Professional Codebase Auditing

    The Tech Debt Scanner is a diagnostic tool designed for developers and engineering leads who need to quantify and prioritize code quality issues. It moves beyond simple linting by analyzing codebases across five critical dimensions: comment debt, structural complexity, dependency health, test coverage gaps, and documentation staleness.

    What it does

    This skill performs a comprehensive, read-only analysis of your repository using standard Unix utilities. It identifies "code smells" and hidden maintenance burdens, such as deeply nested logic, oversized functions, abandoned TODOs, and outdated dependencies. Unlike manual reviews, it provides an objective inventory of issues categorized by severity.

    • Structural Analysis: Detects high cyclomatic complexity and maintenance bottlenecks.
    • Audit Trails: Tracks HACK/FIXME markers and orphaned documentation.
    • Health Metrics: Assesses test-to-source ratios and stale lockfiles.
    • Actionable Reporting: Generates a prioritized Markdown report with specific remediation steps.

    Why use this skill

    While an AI can "look at code," it often struggles to provide a holistic view of technical debt across thousands of files. This skill automates the discovery process, providing a structured data set that you can use for sprint planning, release readiness checks, or onboarding audits. It produces a clear severity-based hierarchy (Critical to Low), making it easy to argue for refactoring time with stakeholders.

    Use Cases

    • Identify high-risk TODOs and FIXMEs across the entire codebase
    • Detect overly complex functions and files that need refactoring
    • Assess test coverage gaps and stale dependencies before a major release
    • Generate documentation for sprint planning to justify refactoring work

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Security Scanned

    Passed automated security review

    Permissions

    Terminal / Shell

    Allowed Hosts

    example.com
    docs.acme.com
    imgur.com

    File Scopes

    references/**
    scripts/**
    assets/**

    Frequently Asked Questions

    More Premium Skills

    Free