01
What this skill does
Use this skill for a narrow Bugbot workflow over local branch or uncommitted changes. Detection inventories tracked and untracked files, recursively follows diff-derived candidates until a bounded fixed point, and persists every verified production bug in a unique Markdown report; that report is its only detection-time write. Repair intent is resolved from the full conversation, including an initial request to review and fix. After persistence, continue authorized repairs without another approval round; review-only requests stop at the report. Clear repair intent with no narrower scope selects all unresolved findings in the latest unambiguous report, while semantic references can select a subset. Run targeted and required checks without silently fixing distinct new findings or mutating Git publication state.
02
When to use it
- 01Reviewing current branch work against the repository default branch or a named base.
- 02Reviewing staged, unstaged, and untracked local changes against HEAD.
- 03Producing an uncapped durable report, then repairing all or selected findings from contextually recognized intent.
03
How it works
- 01
Resolve the repository, comparison mode, baseline, tracked diff, and untracked-file inventory.
- 02
Seed a candidate frontier from every changed hunk and untracked file.
- 03
Trace each candidate only through causally relevant control flow, dependencies, contracts, state, and failure paths.
- 04
Add newly exposed diff-connected risks until the frontier reaches a fixed point, then verify and de-duplicate by root cause.
- 05
Write every distinct verified finding to a unique Markdown report with stable report-local IDs, evidence, coverage, and a recommendation.
- 06
After report persistence, apply existing repair authorization from the initial request or later conversation, reverify the selected findings, and run targeted plus required checks without unnecessary repetition.
04
What you get back
- 01A durable Markdown report with one card per introduced production bug plus a complete findings index.
- 02An explicit clean report when a complete review finds no bugs, or an incomplete report with exact coverage gaps.
- 03A Markdown repair summary after confirmed fixes, including verification and remaining unconfirmed issues.
05
Important boundaries
- 01During detection, write only the report artifact; do not edit reviewed source files or Git state.
- 02Start fresh detection for Bugbot requests; implicit routing exists for report follow-ups, not generic code review.
- 03Resolve repair intent from current and prior user instructions, preserve review-only scope, and ask only when intent, report, or finding scope remains materially unclear.
- 04Do not cap findings or stop after the highest-severity or easiest bugs.
- 05Do not widen the recursive frontier beyond paths causally connected to the reviewed change.
- 06Do not stage, commit, push, deploy, or repair distinct new findings without separate authorization.
06