Run any Skill in Manus with one click

Get Started

debug-reproduce-isolate-fix

Stars17

Forks4

UpdatedJune 7, 2026 at 13:04

Systematically diagnose and fix a bug instead of guessing.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AuraVixStudio

AuraVixStudio/caelo

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	Debug (reproduce -> isolate -> fix)
description	Systematically diagnose and fix a bug instead of guessing.
triggers	["debug","fix bug","why does this fail","investigate error"]

Debug (reproduce -> isolate -> fix)

Use this to track down a bug methodically.

Steps

Reproduce. Get a reliable, minimal repro. If you can't reproduce it, gather the exact error, stack trace, inputs, and environment first.
Isolate. Narrow the failure: read the stack trace, add targeted logging, bisect the input or the recent changes. Form a hypothesis about the root cause.
Confirm root cause. Verify the hypothesis — don't fix symptoms. State why it fails.
Fix. Apply the smallest change that addresses the root cause. Avoid unrelated edits.
Verify + guard. Re-run the repro to confirm the fix, run the broader tests for regressions, and add a test that would have caught this bug.

Notes

Resist guess-and-check. One confirmed root cause beats five speculative edits.
Remove temporary logging/instrumentation before finishing.

More from this repository

same repository

review-a-github-pr-via-gh

AuraVixStudio/caelo

Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the `gh` CLI or the GitHub MCP server.

2026-06-1717

commit-clean-conventional

AuraVixStudio/caelo

Stage the right changes and write a clear, conventional commit message.

2026-06-0717

document-code

AuraVixStudio/caelo

Add clear docstrings/comments and update docs for changed or unfamiliar code.

2026-06-0717

explain-codebase

AuraVixStudio/caelo

Map and explain an unfamiliar codebase or module to the user.

2026-06-0717

refactor-behavior-preserving

AuraVixStudio/caelo

Improve code structure in small, safe steps without changing behavior.

2026-06-0717

write-tests

AuraVixStudio/caelo

Add focused, meaningful tests for code — happy path plus the edge cases that matter.

2026-06-0717

name	Debug (reproduce -> isolate -> fix)
description	Systematically diagnose and fix a bug instead of guessing.
triggers	["debug","fix bug","why does this fail","investigate error"]

Debug (reproduce -> isolate -> fix)

Use this to track down a bug methodically.

Steps

Reproduce. Get a reliable, minimal repro. If you can't reproduce it, gather the exact error, stack trace, inputs, and environment first.
Isolate. Narrow the failure: read the stack trace, add targeted logging, bisect the input or the recent changes. Form a hypothesis about the root cause.
Confirm root cause. Verify the hypothesis — don't fix symptoms. State why it fails.
Fix. Apply the smallest change that addresses the root cause. Avoid unrelated edits.
Verify + guard. Re-run the repro to confirm the fix, run the broader tests for regressions, and add a test that would have caught this bug.

Notes

Resist guess-and-check. One confirmed root cause beats five speculative edits.
Remove temporary logging/instrumentation before finishing.