skills.rest
jayteealao
jayteealaoCOMMUNITY
Explore all skills by this author →
GitHub

technical-debt

Identify and track technical debt with YAML schemas and scoring.

Updated Jan 6, 2026
Search Tags:#patterns#code-quality#scoring#software-engineering#technical#debt
One-click install
npx skills add https://github.com/jayteealao/gitt-gaff --skill technical-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt
Source: https://github.com/jayteealao/gitt-gaff/tree/main/.claude/skills/technical-debt
Command: npx skills add https://github.com/jayteealao/gitt-gaff --skill technical-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical debt slows software delivery and increases maintenance risk by hiding inefficiencies, outdated patterns, and suboptimal decisions.

Core Features & Use Cases

  • Patterns for identifying, categorizing, and tracking debt.
  • YAML schemas for debt files and a scoring methodology.
  • References and guidance for debt resolution workflows across projects.

Quick Start

Identify debt items, score them by impact and effort, and generate a prioritized remediation plan.

Frequently Asked Questions about technical-debt

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

FAQPage Schema
How do I identify and categorize technical debt in my codebase?▼

You identify technical debt by applying patterns to detect code inefficiencies, then categorize findings using a standardized debt taxonomy and record them using a YAML-frontmatter schema for consistent tracking.

What is the best way to score technical debt for prioritization?▼

The best way to score technical debt is by evaluating each item's impact and effort using a standardized scoring methodology, allowing you to generate a prioritized remediation plan based on these metrics.

Can I track technical debt across multiple projects of different sizes?▼

Yes, you can track technical debt across multiple projects, as this approach is applicable to codebases of all sizes and supports consistent debt categorization, scoring, and lifecycle tracking across your software portfolio.

How does a YAML schema help with technical debt resolution workflows?▼

A YAML schema helps technical debt resolution workflows by providing a structured format for debt files, ensuring consistent recording of debt items, their scores, and lifecycle status across different projects and teams.

Do I need specific dependencies to implement a technical debt tracking system?▼

No specific dependencies are required to implement technical debt tracking, as the system provides self-contained reference materials, YAML schemas, and standardized taxonomies that integrate directly into your existing software engineering workflows.

Related Skills

Explore More Software Engineering Skills→
DauQuangThanhDauQuangThanh
14

code-quality-review

Detect code smells and measure complexity in repositories.

Community
Advanced
ValerianGuivarchValerianGuivarch

github-sprint-tracker

Generate sprint summary reports for GitHub pull requests without Jira tickets.

Community
Intermediate
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate
Harshal1841AHarshal1841A

tech-debt-tracker

Detect, analyze, and track technical debt across codebases.

Community
Intermediate