bug-triage_skill

Overview

This skill reproduces, isolates, and fixes a reported bug or failing test, then delivers a concise summary of root cause, fix, and verification steps. It focuses on creating a reliable repro, implementing a minimal fix, and producing clear verification and risk notes for review and merge.

How this skill works

I first collect missing details (repro steps, environment, logs, frequency) and consult repo guidance. I reproduce the failure locally with the repo’s preferred tools, narrow the failure to a file or function, form and validate a root-cause hypothesis, implement the smallest safe fix, and run the project’s standard checks and manual verification steps.

When to use it

• User reports a bug without a clear repro and wants a fix
• A build or test is failing and you want a minimal, reviewed fix
• You need a root-cause explanation for a regression
• You want verification steps and risk notes for a PR
• Triaging flaky tests or intermittent failures

Best practices

• Ask for exact reproduction steps and full unedited logs when info is missing
• Prefer the project’s documented commands (bun/npm/pnpm/yarn) and respect repo-specific guidance
• Reproduce with the simplest, fastest scenario; reduce nondeterminism for flaky failures
• Localize the failure before changing code; avoid drive-by refactors
• Implement the minimal change that fixes the root cause and run lint/tests/build before proposing the PR

Example use cases

• User reports a runtime error in production with a stack trace but no repro—produce local repro and fix
• CI test started failing after a dependency bump—identify regression, bisect if needed, and patch
• A flaky test fails intermittently—stabilize by removing nondeterminism or fixing timing assumptions
• A UI regression report includes screenshots but no steps—recreate the user flow, find the faulty component, and submit a minimal fix