Scan files or folders for technical debt and produce a prioritized triage table.
npx skills add https://github.com/Noegnesis/noesis --skill techdebt-noegnesis
Please help me install this Agent Skill. Skill: techdebt Source: https://github.com/Noegnesis/noesis/tree/main/skills/techdebt Command: npx skills add https://github.com/Noegnesis/noesis --skill techdebt-noegnesis
It helps you quickly understand what is technically wrong or risky in a codebase so you can plan cleanup without guessing or starting a refactor blindly.
Ask for a technical-debt scan by telling the assistant which file or folder you want reviewed, for example: "Run /techdebt on src/ and show the top cleanup priorities."
High-intent search queries and answers about installing and using this skill.
To identify technical debt, run a read-only scan on a specified file or folder to detect code smells, missing tests, magic numbers, untyped boundaries, dead code, and error swallowing. This produces a prioritized triage table to help you plan refactors without guessing.
The best way to prioritize code cleanup is to scan representative entry points and markers like TODO or FIXME to surface technical debt. The scan outputs a ranked table capped at around 15 items, showing exactly where to invest cleanup effort for the highest impact.
You can detect code smells and untyped boundaries through an approval-gated, read-only scan that avoids auto-fixing. It identifies duplication, dead code, and error swallowing, then waits for you to approve specific findings before any changes are proposed.
Yes, you can scan a specific folder for missing tests and dead code by providing the folder path. The scan uses relevant markers and representative entry points to find technical debt and outputs a prioritized list of issues for your review.
A technical debt scan looks for long functions, duplication, magic numbers and strings, missing tests, dead code, error swallowing, and coupling. It aggregates these code smells into a prioritized triage table to guide your refactoring planning.
No, a technical debt scan is strictly read-only and does not automatically modify source files. It generates a prioritized triage table of findings and explicitly requests your approval before proposing any specific fixes.
nikhillinitDetect and prioritize technical debt with configurable thresholds and SQALE metrics.
rom-orlovichRefactor Python codebases incrementally with tests to preserve behavior.
Sir-chawakornRefactor codebases using static analysis to ensure behavioral equivalence.
gideonshakedAudit code for bugs, dead code, technical debt, and architectural issues.
