techdebt

Detect and remediate technical debt in JavaScript, TypeScript, Python, and Rust codebases.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill techdebt-sburl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/techdebt
Command: npx skills add https://github.com/sburl/CrossCheck --skill techdebt-sburl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical debt accumulates during development and review; this skill automates detection and remediation to keep code healthy and maintainable.

Core Features & Use Cases

  • Automated debt detection: identifies silenced linter issues, stray debug statements, and TODO/FIXME comments.
  • Optional deep checks: when tools are available, analyzes code duplication, dead code, and circular dependencies.
  • PR-ready reporting: summarizes findings and can auto-fix straightforward issues to streamline PR workflows.

Quick Start

Run /techdebt to automatically detect and fix critical debt issues in your codebase.

Frequently Asked Questions about techdebt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically find and fix technical debt in my codebase?

You can detect technical debt by running automated static analysis that identifies silenced linter issues, stray debug statements, and TODO/FIXME comments, then auto-fixes straightforward issues to streamline pull request workflows.

Can I enforce linting and code quality checks for JavaScript and Python projects?

Yes, you can enforce linting and code quality checks for JavaScript, TypeScript, and Python projects by automatically detecting silenced errors, console statements, and TODO comments during development and review.

How do I detect circular dependencies and dead code during code review?

To detect circular dependencies and dead code during code review, run deep static analysis checks if the relevant tools are installed, allowing the system to identify duplicated code and structural issues automatically.

Does automated technical debt detection work with Rust codebases?

Yes, automated technical debt detection works with Rust codebases, applying linting enforcement and identifying TODO comments, plus optional deep checks for dead code and circular dependencies when tools are available.

What is the best way to clean up stray debug statements and TODO comments before merging a pull request?

The best way to clean up stray debug statements and TODO comments before merging is to run automated detection that scans for these issues and generates PR-ready reports, auto-fixing straightforward problems to streamline workflows.

Do I need extra tools installed to check for code duplication and dead code?

Yes, you need the relevant analysis tools installed to perform optional deep checks for code duplication, dead code, and circular dependencies, though standard checks for linting and TODOs require no extra tools.