skills.rest
reiserwang
reiserwangCOMMUNITY
Explore all skills by this author →
GitHub

techdebt

Scan codebases for TODO/FIXME tags, complexity, and duplicated logic, then generate tech_debt_report.md and implementation_plan.md.

Updated Aug 27, 2026
Search Tags:#architecture#audit#complexity#refactor#code-quality#static-analysis#tech-debt
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill techdebt-reiserwang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/techdebt
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill techdebt-reiserwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the codebase to identify technical debt, duplicated patterns, and standards violations, then produces a structured remediation plan.

Core Features & Use Cases

  • Scan the repository to locate TODO, FIXME, HACK, and XXX tags and assess their severity.
  • Identify high-complexity files and potential architectural duplications to surface refactor opportunities.
  • Generate a prioritized audit artifact and an actionable implementation plan to guide maintenance, modernization, and onboarding.

Quick Start

Run the techdebt skill on a target repository to generate a remediation plan.

Frequently Asked Questions about techdebt

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

FAQPage Schema
How do I audit my codebase for technical debt and standards violations?▼

Scanning your codebase for technical debt identifies TODO, FIXME, HACK, and XXX tags, assesses their severity, and detects high-complexity files to produce a structured remediation plan.

What is the best way to find duplicated logic and refactor opportunities in a project?▼

Identifying duplicated logic and refactor opportunities requires scanning the codebase to surface architectural duplications and high-complexity files, which produces an actionable implementation plan for maintenance.

Can I use static analysis to plan refactors for projects of varying sizes and languages?▼

Static analysis can plan refactors for projects of varying sizes and languages by assessing code complexity and standards violations, guiding maintenance, modernization, and onboarding processes.

How do I generate an implementation plan for code maintenance and modernization?▼

Generating an implementation plan for code maintenance involves auditing the repository for technical debt and architectural duplications, then outputting an actionable implementation_plan.md to guide modernization.

Does technical debt scanning detect TODO and FIXME tags across the entire repository?▼

Technical debt scanning detects TODO and FIXME tags across the repository, assesses their severity, and includes them in the generated tech_debt_report.md audit artifact.

Related Skills

Explore More Software Engineering Skills→
mahmoud20138mahmoud20138
10

generate-snapshot

Generate a codebase health snapshot analyzing git history, complexity, debt markers, and dependencies.

Community
Advanced
cosmixcosmix
53

refactoring

Refactor legacy code using Extract Method and other patterns while preserving behavior.

Community
Advanced
zgagnonzgagnon
1

adr-review

Review code against project ADRs and report violations with fixes.

Community
Advanced
abhishekdutta18abhishekdutta18

plankton-code-quality

Run formatters and linters to enforce code quality during file edits.

Community
Intermediate