skills.rest
cyberpunk042
cyberpunk042COMMUNITY
Explore all skills by this author →
GitHub

quality-debt

Scan code markers and wiki backlog to generate a prioritized debt audit.

Updated Mar 26, 2026
Search Tags:#inventory#tech-debt#workarounds#code-markers#deferred-tasks#structural-gap#operational-gap
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill quality-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-debt
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/quality-debt
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill quality-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inventory known technical debt across code, wiki, and architecture, surfacing gaps that slow work and risk regressions.

Core Features & Use Cases

  • Marker-based debt discovery: scans code for TODO/FIXME/XXX/HACK and catalogs location, type, and age to reveal true risk.
  • Deferred work tracking: reads wiki backlog tasks with status blocked or deferred to capture why work was postponed and target milestones.
  • Structural vs operational gaps: surfaces wiki decisions and structural stubs that impede delivery, so teams can align architecture with practice.
  • Workaround documentation: identifies and records documented workarounds and their context to avoid reintroducing risk.
  • Actionable outputs: writes a dated debt-audit page and surfaces follow-up tasks to address the highest-priority items.

Quick Start

To begin an audit, load the debt inventory operator and trigger an inventory pass.

Frequently Asked Questions about quality-debt

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

FAQPage Schema
How do I inventory tech debt across code and wiki documentation?▼

Tech debt inventory is generated by scanning code for TODO/FIXME/XXX/HACK markers and reading wiki backlog tasks to surface structural and operational gaps, producing a dated debt-audit page with a prioritized task plan.

What is the best way to track deferred tasks and workarounds before a release?▼

Tracking deferred tasks and workarounds before a release involves logging documented workarounds and reading backlog tasks with blocked or deferred status to capture context, target milestones, and generate a prioritized debt inventory.

Can I generate a technical debt audit for contributor onboarding?▼

Yes, a technical debt audit for contributor onboarding applies marker-based debt discovery and structural gap analysis to generate a dated debt-audit page and a structured task plan, surfacing known risks and deferred work.

How do code markers like TODO and FIXME help identify technical debt?▼

Code markers like TODO and FIXME help identify technical debt by cataloging their location, type, and age during a scanning pass, revealing the true risk and scope of deferred work embedded in the codebase.

What is the difference between structural and operational gaps in a tech debt audit?▼

Structural gaps in a tech debt audit surface wiki decisions and architecture stubs that impede delivery, while operational gaps identify documented workarounds and their context to avoid reintroducing risk during ongoing work.

Related Skills

Explore More Software Engineering Skills→
berkcangumusisikberkcangumusisik
11

tech-debt

Audit codebases to catalog technical debt into a prioritized backlog.

Community
Intermediate
TruCol270TruCol270
1

gsd-plan-milestone-gaps

Convert milestone audit gaps into actionable phases in ROADMAP.md.

Community
Advanced
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
Kirankumar2604Kirankumar2604

follow-up-tasks

Proposes secondary work items categorized bytech debt, gaps, and deferred features for a task tracking API.

Community
Basic