capture-review-debts

Capture and triage technical debt into structured GitHub issues.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill capture-review-debts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-review-debts
Source: https://github.com/fsolla/teqo/tree/main/.cursor/skills/capture-review-debts
Command: npx skills add https://github.com/fsolla/teqo --skill capture-review-debts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented or lost technical debt and product improvements identified during intensive coding sessions, ensuring that valuable insights from simplify or impeccable reviews are tracked and prioritized rather than forgotten.

Core Features & Use Cases

  • Intelligent Triage: Categorizes findings by importance and decision type, distinguishing between expensive locks, polish, and deferrable tasks.
  • Automated Registration: Streamlines the creation of GitHub issues or plans for approved debts, preventing backlog pollution.
  • Use Case: After a complex refactoring session, use this skill to harvest all remaining cleanup items, deduplicate them against existing plans, and register only the high-priority tasks as tracked issues.

Quick Start

Run the capture-review-debts skill to analyze the current session findings and generate a triage table for approval.

Frequently Asked Questions about capture-review-debts

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

FAQPage Schema
How do I track technical debt found during refactoring sessions?

Tracking technical debt found during refactoring sessions involves analyzing session transcripts to deduplicate findings against existing repository states and project roadmaps. This process categorizes tasks by priority and appetite before registering them as structured GitHub issues.

What is the best way to triage technical debt into GitHub issues?

Triage of technical debt into GitHub issues utilizes decision-quality frameworks to categorize findings by importance, distinguishing between expensive locks, polish, and deferrable tasks. This prevents backlog pollution by registering only approved, high-priority items.

How do I prevent backlog pollution when registering product improvements?

Preventing backlog pollution when registering product improvements requires deduplicating session findings against existing development plans and roadmaps. Automated triage enforces strict categorization by technical necessity before executing registration commands.

Can I deduplicate technical debt findings against an existing project roadmap?

Deduplicating technical debt findings against an existing project roadmap is supported by analyzing critique snapshots and session transcripts. The system compares newly identified items against the current repository state to eliminate redundant entries.

How do I categorize technical debt by priority and appetite?

Categorizing technical debt by priority and appetite is achieved through intelligent triage mechanisms that enforce decision-quality frameworks. These frameworks distinguish between expensive locks, polish, and deferrable tasks to ensure proper task prioritization.