skills.rest
striderZA
striderZACOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Scan codebases for debt indicators and maintain a prioritized debt register.

72|7|Updated Apr 29, 2026
Search Tags:#documentation#maintainability#technical debt#prioritization#sprint planning#risk register#code scanning
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill tech-debt-striderza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/tech-debt
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill tech-debt-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify, organize, and prioritize technical debt so teams can address maintainability risks instead of letting them compound silently.

Core Features & Use Cases

  • Codebase scanning: Finds common debt indicators like TODO/FIXME/HACK comments, deprecated markers, duplication, and overly large files/functions.
  • Debt register management: Lets you add debt entries, then keep them updated in a consistent register file.
  • Prioritization and reporting: Re-sorts the register by an impact/frequency/effort score and generates sprint-oriented trend summaries.

Quick Start

Run the tech-debt skill with the scan subcommand to analyze the repository and capture findings for review.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I track and prioritize technical debt in my codebase?▼

The prioritization mechanism scores debt entries by impact, frequency, and remediation effort, re-sorting the register to produce actionable remediation ordering that directly fits your sprint planning and release workflows.

What indicators does a technical debt scan look for in source code?▼

Scanning identifies common debt indicators including TODO/FIXME/HACK comments, deprecated markers, duplication, and overly large files or functions to capture measurable maintainability risks for review.

How do I generate a technical debt report for sprint planning?▼

Running the report subcommand generates sprint-oriented trend summaries by re-sorting the debt register according to impact, frequency, and effort scores, providing recurring trend visibility across releases.

Can I maintain a technical debt register in a markdown documentation file?▼

Yes, the skill reads and optionally writes to a docs/tech-debt-register.md file to maintain debt entries consistently, enforcing user confirmation for writes to prevent unauthorized modifications.

Does the technical debt scanning require any external code analysis dependencies?▼

No, the skill has no external dependencies and operates with deterministic subcommand-driven behavior to scan for debt indicators, add entries, prioritize risks, and generate reports.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

tech-debt

Scan codebase markers and update the technical debt register.

Community
Advanced
brand6brand6

tech-debt

Scan codebases to identify technical debt and update a prioritized debt register.

Community
Intermediate
nuoyanruoshuinuoyanruoshui
47

tech-debt

Scan codebases for debt indicators and manage prioritized debt registers.

Community
Advanced
thechandanbhagatthechandanbhagat
8

code-review

Automate code reviews to detect security issues and maintainability problems.

Community
Basic