Run any Skill in Manus with one click

trace-bug

Stars7

Forks0

UpdatedMay 17, 2026 at 10:52

Use when the user asks why a bug happens, wants an explanation grounded in code, or says to check the real code/data path before fixing. Also use for missing data, inconsistent UI state, broken workflows, and suspected backend/frontend contract issues.

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

buhaistrikalo

buhaistrikalo/skills

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

File Explorer

2 files

SKILL.md

readonly

name	trace-bug
description	Use when the user asks why a bug happens, wants an explanation grounded in code, or says to check the real code/data path before fixing. Also use for missing data, inconsistent UI state, broken workflows, and suspected backend/frontend contract issues.
metadata	{"short-description":"Trace bugs from real code paths"}

Trace Bug

Find the real source of a bug before proposing or making a fix.

Workflow

Start from the symptom.
- Identify the exact user-visible behavior.
- Find the route, component, command, endpoint, job, or database field involved.
- Do not ask for credentials if local code already explains the likely path.
Trace the source of truth.
- Follow data from persistence/API to UI or from UI action to backend handler.
- Prefer real code references over guesses.
- Distinguish display transforms from stored data.
Explain the cause.
- State where the behavior comes from.
- Separate confirmed facts from assumptions.
- Name the smallest place where the fix belongs.
Fix only when requested or clearly implied.
- Prefer root-cause fixes over masking symptoms.
- Keep the diff scoped to the traced path.
- Add targeted validation when the behavior can regress.

Output

root cause
relevant code path
fix made or recommended
verification performed

More from this repository

same repository

skill-maker

buhaistrikalo/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

2026-06-117

grill-with-docs

buhaistrikalo/skills

Use when the user wants to stress-test a plan against the project's existing domain language, glossary, code behavior, and documented decisions. Also use when they mention grilling a plan, sharpening terminology, walking a design tree, updating CONTEXT.md, or deciding whether an ADR is needed.

2026-06-077

handoff

buhaistrikalo/skills

Use when the user wants to compact the current conversation into a handoff document for another agent or future session to continue the work. Also use when they mention handoff, transfer context, continue in a new session, or summarize the session for the next agent.

2026-05-307

figma-fix

buhaistrikalo/skills

Use when the user provides a Figma node, screenshot, or visual reference and wants a narrow frontend change to match it. Also use for small UI copy, layout, spacing, state, or component adjustments driven by a concrete design reference.

2026-05-177

push-to-main

buhaistrikalo/skills

Use when the user asks to push, upload, publish, or "залей" changes to main. Also use when they provide a GitHub remote and want the current repository committed and pushed.

2026-05-177

small-diff

buhaistrikalo/skills

Use when a change has become too large, the user worries about extra lines or overengineering, or asks to simplify, reduce scope, avoid unrelated changes, or keep only the necessary diff.

2026-05-177

name	trace-bug
description	Use when the user asks why a bug happens, wants an explanation grounded in code, or says to check the real code/data path before fixing. Also use for missing data, inconsistent UI state, broken workflows, and suspected backend/frontend contract issues.
metadata	{"short-description":"Trace bugs from real code paths"}

Trace Bug

Find the real source of a bug before proposing or making a fix.

Workflow

Start from the symptom.
- Identify the exact user-visible behavior.
- Find the route, component, command, endpoint, job, or database field involved.
- Do not ask for credentials if local code already explains the likely path.
Trace the source of truth.
- Follow data from persistence/API to UI or from UI action to backend handler.
- Prefer real code references over guesses.
- Distinguish display transforms from stored data.
Explain the cause.
- State where the behavior comes from.
- Separate confirmed facts from assumptions.
- Name the smallest place where the fix belongs.
Fix only when requested or clearly implied.
- Prefer root-cause fixes over masking symptoms.
- Keep the diff scoped to the traced path.
- Add targeted validation when the behavior can regress.

Output

root cause
relevant code path
fix made or recommended
verification performed