skills.rest
yabafre
yabafreCOMMUNITY
Explore all skills by this author →
GitHub

aped-debug

Diagnose failing tests by reproducing bugs and validating root-cause hypotheses.

2|Updated Mar 12, 2026
Search Tags:#test automation#debugging#root cause analysis#hypothesis testing#instrumentation#regression testing#debug feedback loop
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aped-debug
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-debug
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It helps you troubleshoot failing software by forcing a disciplined loop: build a deterministic feedback signal, reproduce the exact failure, generate falsifiable hypotheses, instrument safely, then apply the smallest fix with a regression test and a clean post-mortem.

Core Features & Use Cases

  • Disciplined diagnosis loop: Build a fast pass/fail feedback loop, reproduce the bug, hypothesize ranked causes, instrument one variable at a time, and iterate until the root cause is validated.
  • 3-failed-fixes safeguard: Stops after three failed attempts to prevent endless patching when the underlying assumption is wrong.
  • Evidence-driven cleanup & post-mortem: Ensures tagged debug probes are removed and commits capture cause + falsified hypotheses for future discovery.
  • Invocation-context aware: Runs as standalone, from aped-dev (persistent test red), or from aped-review (root-cause finding routing).

Quick Start

Use the aped-debug skill when you see tests failing or you’re stuck debugging a production issue, and ask it to find the root cause from the exact failure description.

Frequently Asked Questions about aped-debug

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

FAQPage Schema
How do I find the root cause of a failing test regression?▼

Debug failing test regressions by running a disciplined feedback-loop workflow that builds a deterministic reproducer, generates ranked hypotheses, and instruments one variable at a time to validate the root cause.

What is the best way to stop endlessly patching a bug when my fixes keep failing?▼

Prevent endless patching by applying a three-failed-fixes stopping rule that halts iteration after three failed attempts, forcing a reassessment of the underlying root-cause hypothesis.

How do I safely instrument code for debugging without leaving test artifacts behind?▼

Safely debug code by instrumenting one variable at a time with tagged probes, then perform evidence-driven cleanup to remove all debug tags before shipping.

How do I structure a post-mortem after diagnosing a hard bug?▼

Structure a bug post-mortem by writing commits that capture the validated root cause and falsified hypotheses for future discovery, followed by a fix-before-ship regression test sequence.

Can I use a disciplined debugging workflow for performance regressions?▼

Yes, you can diagnose performance regressions by applying the same disciplined feedback-loop workflow to build a deterministic reproducer and validate root-cause hypotheses.

Related Skills

Explore More Software Engineering Skills→
vTRKAvTRKA

systematic-debugging

Reproduce and localize test, runtime, integration, or environment failures with evidence.

Community
Advanced
VrooliVrooli
54

Scientific Debugging

Generate falsifiable hypotheses and validation tests to diagnose root causes.

Official
Advanced
LeonardoTan19LeonardoTan19
2

systematic-debugging

Enforce root-cause analysis before applying fixes across debugging phases.

Community
Advanced
TakfesTakfes

plan-and-critique

Structures open-ended planning into a disciplined critique and revision loop.

Community
Advanced