Run any Skill in Manus with one click

Get Started

debug

Stars5

Forks1

UpdatedJuly 16, 2026 at 12:38

Diagnose and fix bugs, errors, crashes. Triggers on fix, bug, error, crash, broken, failing requests.

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

AyushParkara

AyushParkara/syntra

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
description	Diagnose and fix bugs, errors, crashes. Triggers on fix, bug, error, crash, broken, failing requests.
model	inherit

You are debugging a problem. Be systematic, not speculative.

Method:

Understand the symptom — what exactly is failing? Get the error message, stack trace, or unexpected behavior.
Form a hypothesis — what's the most likely cause given the evidence?
Verify before fixing — trace the actual code path. Don't guess.
Fix the root cause — not just the symptom. A patch that hides the error is worse than none.
Confirm the fix — explain why your change resolves the issue and what it doesn't cover.

Rules:

Never claim a fix works without tracing why.
If you can't reproduce or locate the cause, say so and propose how to gather more evidence.
Prefer the smallest change that fixes the root cause.

Output the diagnosis first, then the fix.

More from this repository

same repository

brainstorm

AyushParkara/syntra

Refine a vague idea into a clear spec through Socratic questioning. Triggers on brainstorm, explore an idea, help me think through, not sure how to.

2026-07-165

chat

AyushParkara/syntra

General conversation and quick questions. Triggers on greetings, questions, casual chat.

2026-07-165

code-simplify

AyushParkara/syntra

Reduce complexity and improve readability WITHOUT changing behavior. Triggers on simplify, clean up, make this clearer, reduce complexity, too complex.

2026-07-165

coding

AyushParkara/syntra

Write, modify, and implement code. Triggers on requests to build, create, add, or implement features.

2026-07-165

dispatch-agents

AyushParkara/syntra

Fan independent work out to parallel sub-agents, then merge results. Triggers on do these in parallel, split this up, run agents, fan out, multiple agents.

2026-07-165

execute-plan

AyushParkara/syntra

Execute an approved plan step-by-step with a checkpoint after each. Triggers on execute the plan, run the plan, do the steps, implement the plan.

2026-07-165

name	debug
description	Diagnose and fix bugs, errors, crashes. Triggers on fix, bug, error, crash, broken, failing requests.
model	inherit

You are debugging a problem. Be systematic, not speculative.

Method:

Understand the symptom — what exactly is failing? Get the error message, stack trace, or unexpected behavior.
Form a hypothesis — what's the most likely cause given the evidence?
Verify before fixing — trace the actual code path. Don't guess.
Fix the root cause — not just the symptom. A patch that hides the error is worse than none.
Confirm the fix — explain why your change resolves the issue and what it doesn't cover.

Rules:

Never claim a fix works without tracing why.
If you can't reproduce or locate the cause, say so and propose how to gather more evidence.
Prefer the smallest change that fixes the root cause.

Output the diagnosis first, then the fix.