skills.rest
ddmanyes
ddmanyesCOMMUNITY
Explore all skills by this author →
GitHub

sp-fix-test

Guide four-phase debugging to reproduce, localize, analyze, and verify failing tests.

Updated Apr 20, 2026
Search Tags:#testing#debugging#logs#verification#localization#reproduction#root-cause-analysis
One-click install
npx skills add https://github.com/ddmanyes/antigravity-skills-zht --skill sp-fix-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-fix-test
Source: https://github.com/ddmanyes/antigravity-skills-zht/tree/main/skills/sp-fix-test
Command: npx skills add https://github.com/ddmanyes/antigravity-skills-zht --skill sp-fix-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When tests fail or bugs appear, this Skill provides a disciplined four-phase debugging method to reproduce, localize, analyze, and verify fixes, reducing guesswork and speeding resolution.

Core Features & Use Cases

  • Reproduction: construct a minimal, reliable failing test case to reproduce the issue.
  • Localization: use logs, stack traces, and debuggers to narrow down where the problem occurs.
  • Root Cause Analysis: understand why the failure happens, including edge cases and unexpected interactions.
  • Verification: implement fixes and validate through re-run tests and regression checks.

Quick Start

Activate the four-phase debugging workflow to systematically reproduce, localize, analyze, and verify a failing test.

Frequently Asked Questions about sp-fix-test

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

FAQPage Schema
What is a systematic approach to debugging failing unit tests?▼

A systematic debugging method for failing tests uses a four-phase process: reproduce the issue, localize the fault, analyze the root cause, and verify the fix. This structured approach reduces guesswork by enforcing reliable reproduction and root-cause analysis.

How do I find the root cause of a failing test using stack traces and logs?▼

To find the root cause of a failing test, use logs and stack traces during the localization phase to narrow down where the problem occurs. This isolates the exact code path before you analyze why the failure happens.

What do I need to reproduce a failing test case for debugging?▼

Reproducing a failing test case requires a minimal reproducible example, access to logs and stack traces, and the discipline to verify changes one at a time. This minimal setup reliably triggers the issue for root-cause analysis.

What is the best way to verify a code fix for a failing unit test?▼

The best way to verify a code fix is to implement the change and validate it through re-running tests and regression checks. This ensures the original failure is resolved without introducing unexpected interactions.

Can I use this debugging workflow for any codebase or programming language?▼

Yes, this debugging workflow targets diverse codebases by focusing on universal debugging phases. It requires a minimal reproducible example, access to logs, and stack traces, making it applicable across different programming environments.

Related Skills

Explore More Software Engineering Skills→
jMertajMerta
130

bug-triage

Convert ambiguous bug reports into reproducible repros, root-cause explanations, and minimal fixes.

Community
Advanced
StudentCristianStudentCristian

nw-bugfix

Coordinate root-cause analysis, user validation, and regression testing for defect resolution.

Community
Advanced
santosomarsantosomar
1

test-guided-bug-detector

Analyze failing test results to localize and identify software bugs.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced