che-debugger-bugfix

Diagnose and fix bugs through a hypothesis-driven reproduce-instrument-analyze loop with regression tests.

Updated May 12, 2026
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-debugger-bugfix-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-debugger-bugfix
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-debugger-bugfix
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-debugger-bugfix-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Fixing bugs without a systematic method leads to shotgun edits, unfixed root causes, and regressions. This Skill enforces a scientific debugging loop: reproduce the bug first, lock it with a failing automated test, iterate ranked hypotheses with targeted instrumentation, then apply a minimal verified fix. ## Core Features & Use Cases - Repro Automation Lock: Blocks any code edit until the bug is reproduced as a failing automated test (Vitest, Playwright, pytest), creating a deterministic regression lock that must flip green after the fix. - Hypothesis-Driven Debug Loop: Ranks 3 candidate root causes, then iterates hypothesize → instrument → reproduce → analyze (max 5 iterations) with mandatory per-iteration evidence logged to a session file. - Minimal Fix + Handoff Report: Applies only the lines that fix the root cause, forbids drive-by refactoring, and produces a before/after proof-of-work report with manual verification steps. - Use Case: A user reports that a refund succeeds but the row status never updates. The Skill asks for expected behavior and reproduction steps, writes a failing integration test, instruments the refund flow, confirms the root cause hypothesis, applies the minimal fix, and delivers a verification guide. ## Quick Start Describe the bug with its expected behavior, actual behavior, and numbered reproduction steps, then ask the agent to debug and fix it using the scientific debug loop.

Frequently Asked Questions about che-debugger-bugfix

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

FAQPage Schema
How do I fix a bug using a scientific debugging process?▼

Provide the expected behavior, actual behavior, and numbered reproduction steps. The debugger reproduces the bug, writes a failing automated test as a regression lock, iterates ranked hypotheses with instrumentation, then applies a minimal verified fix.

What is a reproduction automation lock in debugging?▼

It is a hard gate requiring the bug to be reproduced as a failing automated test (Vitest, Playwright, or pytest) before any hypothesis or code edit. The same test must pass after the fix without changing its body, proving the root cause was addressed.

What information do I need to provide before a bug can be debugged?▼

You must provide the expected behavior, the actual buggy behavior including stack traces or error messages, and minimal numbered reproduction steps with route, credentials, and environment details. A ticket reference is optional.

What happens if the bug cannot be reproduced automatically?▼

The debugger stops and asks for an explicit override with a justification before proceeding. If reproduction fails entirely, it returns clarifying questions about version, role, seed data, or branch differences instead of guessing fixes.

Does this debugging approach allow refactoring during a bugfix?▼

No. Bugfixes are limited to the minimal lines that fix the confirmed root cause. Adjacent issues are logged for a separate follow-up PR, and all temporary debug logging must be removed before handoff.

What happens if the root cause is not found after several iterations?▼

After 5 iterations without a confirmed fix, the debugger reports all refuted hypotheses with evidence, states the strongest remaining hypothesis, and offers next steps such as more iterations, additional context, or a pairing session.