skills.rest
foomakers
foomakersOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pair-capability-assess-debt

Assess technical debt across code, design, testing, documentation, and infrastructure.

6|Updated Aug 3, 2025
Search Tags:#code quality#refactoring#remediation#technical debt#prioritization#assessment
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-capability-assess-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pair-capability-assess-debt
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-capability-assess-debt
Command: npx skills add https://github.com/foomakers/pair --skill pair-capability-assess-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the identification, categorization, and prioritization of technical debt within a codebase, providing actionable insights for remediation.

Core Features & Use Cases

  • Automated Debt Detection: Scans code, design, tests, documentation, and infrastructure for various debt indicators.
  • Prioritization Framework: Applies an Impact x Effort formula to rank debt items by severity (High, Medium, Low).
  • Remediation Planning: Suggests strategies for addressing high-priority debt and can trigger decision recording for architectural changes.
  • Use Case: Before merging a pull request, run this Skill to automatically identify any new technical debt introduced, assess its severity, and ensure critical issues are flagged for immediate attention.

Quick Start

Run the pair-capability-assess-debt skill to scan the current codebase for technical debt.

Frequently Asked Questions about pair-capability-assess-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?▼

Technical debt is identified by scanning code, design, tests, documentation, and infrastructure for debt indicators. The assessment categorizes items into distinct domains and scores them based on impact and resolution effort.

How do I prioritize technical debt for remediation?▼

Prioritize technical debt using an Impact x Effort formula that ranks items by severity. This framework scores categorized debt items to recommend actionable remediation strategies for high-priority issues.

Can I automatically detect new technical debt before merging a pull request?▼

Yes, you can run an automated debt detection scan before merging a pull request. This identifies newly introduced technical debt, assesses its severity, and flags critical issues for immediate attention.

What areas of a software project does technical debt assessment cover?▼

Technical debt assessment covers code, design, testing, documentation, and infrastructure. It scans these specific areas to detect various debt indicators and applies a defined resolution cascade for remediation.

When should I use an automated technical debt assessment in my workflow?▼

Use automated technical debt assessment during code review processes or before pull requests. It supports independent invocation or composition within reviews to trigger decision recording for architectural changes.

Does assessing technical debt require specific environment setup or dependencies?▼

Assessing technical debt requires no external dependencies. The assessment operates independently or composes within existing review processes to evaluate code, design, tests, documentation, and infrastructure.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
cslsoftwarescslsoftwares

quality-tech-debt-tracker

Register, classify, and prioritize technical debt with maintenance costs and remediation paths.

Community
Advanced
bitwardenbitwarden
129

reviewing-incremental-changes

Re-review only changed lines in pull requests after developer updates.

Official
Basic
openyakopenyak
704

tech-debt

Identify and prioritize technical debt across codebases using Impact, Risk, and Effort scoring.

Official
Intermediate