skills.rest
app-vitals
app-vitalsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

test-debt

Calculate corrective-commit ratios from git history to measure milestone planning debt.

9|2|Updated Jun 6, 2026
Search Tags:#git#roadmap#test-readiness#milestone-analysis#corrective-commits#planning-debt
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill test-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-debt
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/test-debt
Command: npx skills add https://github.com/app-vitals/shipwright --skill test-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill exposes planning debt that hides behind successful milestone completion by measuring how much corrective churn was needed after tasks were declared done.

Core Features & Use Cases

  • Milestone-level analysis: Calculates a corrective-commit ratio for each milestone instead of blending all work into one noisy summary.
  • Correction pattern detection: Identifies fix, revert, retry, and follow-up commits that indicate the original task was underspecified or misunderstood.
  • Actionable reporting: Writes a structured test-debt report that flags risky milestones, breaks down the worst offending tasks, and adds planning notes for the next roadmap cycle.
  • Example use case: After a release milestone closes, the Skill can show that many follow-up fixes were concentrated in one task, revealing that the task was too large or its acceptance criteria were unclear.

Quick Start

Ask the assistant to analyze the repository history against the test-readiness plan and generate the test-debt report for the completed milestone.

Frequently Asked Questions about test-debt

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

FAQPage Schema
How do I measure planning debt from git history after a milestone?▼

Measuring planning debt from git history involves calculating corrective-commit ratios to identify fix, revert, and follow-up commits after milestone completion. This exposes hidden churn indicating over-specified tasks or ambiguous acceptance criteria.

What is a corrective-commit ratio in test-readiness workflows?▼

A corrective-commit ratio in test-readiness workflows quantifies the proportion of fix, revert, and retry commits following a milestone. It diagnoses scope underestimation and ambiguous acceptance criteria by detecting underspecified tasks in git history.

How do I generate a test-debt report for completed milestones?▼

Generating a test-debt report requires a git repository and milestone task IDs from docs/test-readiness/test-readiness-plan.md. The process applies commit-message pattern matching against dates to output docs/test-readiness/test-debt.md, flagging risky milestones.

Can I detect ambiguous acceptance criteria using commit history?▼

Detecting ambiguous acceptance criteria using commit history is possible by identifying concentrated follow-up fixes. Corrective commits reveal that original tasks were underspecified or misunderstood, directly exposing planning debt after milestone completion.

Does milestone analysis require a specific test-readiness plan file?▼

Milestone analysis requires milestone task IDs and dates from docs/test-readiness/test-readiness-plan.md. Without this test-readiness plan file, the Skill cannot map commit-message patterns to specific milestones to calculate planning debt.

What are the limitations of using corrective commits to assess task readiness?▼

Using corrective commits to assess task readiness is limited by its reliance on commit-message pattern matching. It cannot diagnose over-specified tasks or scope underestimation if corrective churn lacks distinct fix, revert, or retry labels in git history.

Related Skills

Explore More Software Engineering Skills→
app-vitalsapp-vitals
9

test-publish

Publish a test-readiness plan as labeled GitHub issues with a tracking issue.

Official
Advanced
adolfoaranaes12adolfoaranaes12
2

refine-story

Refine vague user stories into sprint-ready narratives with acceptance criteria and test scenarios.

Community
Advanced
wanderinglanternwanderinglantern

policydb-timeline

Generate and maintain policy milestone timelines with health scoring and follow-up updates.

Community
Advanced
DonTiziDonTizi
2

release

Automate Python project releases with version bumps, changelog updates, and Git tags.

Community
Advanced