yellow-debt

Run comprehensive technical debt audit with parallel scanner agents. Use when you need to assess codebase health, identify AI-generated debt patterns, or scan for technical debt.

Agent-driven remediation of specific debt findings with human approval. Use when you want to fix a specific technical debt item.

Validate debt audit prerequisites and optional Linear integration. Use when first installing the plugin or when debt commands fail before scanning begins.

Dashboard of current technical debt levels. Use when you want to check debt status, see aggregated metrics, or export debt data.

Push accepted debt findings to Linear as issues. Use when you want to track technical debt in Linear.

Interactive review and prioritization of pending debt findings. Use when you need to accept, reject, or defer findings from an audit.

Implement fixes for specific technical debt findings with human approval. Use when remediating accepted debt items.

AI-specific anti-pattern detection. Use when auditing code for excessive comments, boilerplate, over-specification, or other AI-generated debt patterns.

Architecture and module design analysis. Use when auditing code for circular dependencies, god modules, boundary violations, or structural issues.

Cyclomatic and cognitive complexity analysis. Use when auditing code for high complexity, deep nesting, and god functions.

Code duplication and near-duplicate detection. Use when auditing code for repeated patterns, copy-paste code, or duplicate logic.

Security-related technical debt detection. Use when auditing code for missing validation, hardcoded config, deprecated crypto, or security debt patterns (not active vulnerabilities).

Merge scanner outputs, deduplicate findings, score severity, and generate reports. Use when synthesizing results from multiple debt scanners.

Technical debt scoring framework and scanner patterns. Use when scanner agents need scoring rubrics, category definitions, safety rules, or output schemas.

1 hook across 1 event