Results for “bugbug”

Investigates bugs, regressions, and crashes by dispatching four parallel read-only sub-agents, then ranks hypotheses and recommends the fastest proof or fix path.

Systematically find and fix bugs using proven debugging techniques, tracing from symptoms to root cause, implementing fixes, and preventing regression.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.

Turns a pile of bugs, issues, and error reports into a ranked, actionable plan with reproduction evidence. Ingests GitHub issues via gh, TODO/FIXME scans, error logs, or a pasted list; attempts to reproduce or classify every item; scores by impact, frequency, fix cost, and regression risk; clusters duplicates; and.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, using a structured checklist and verification process.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Provides a structured debugging workflow for non-technical founders, covering reproduction, diagnostic gathering, and AI-assisted fixes.

Bug Fleet

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and verification steps.

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Diagnoses and fixes bugs in emergency mode with a maximum of two iterations, then commits, pushes, and creates a pull request.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

Provides a structured debugging workflow for diagnosing errors, test failures, and unexpected behavior, including root cause analysis and fix verification.

Runs a disciplined debugging loop for hard bugs and performance regressions, covering reproduction, hypothesis testing, instrumentation, fixing, and regression testing.

Creates professional GitHub issues—bug reports, feature requests, and technical tasks—with clear context, acceptance criteria, and labels for immediate action.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Initializes bug bounty hunt workspaces, logs vulnerability findings with severity and evidence, and enriches them throughout a session.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

Provides structured debugging guidance for errors, test failures, and unexpected behavior, including root cause analysis and verification steps.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Diagnose and fix a bug through a disciplined reproduce, isolate, diagnose, fix, verify loop driven by evidence and one hypothesis at a time — not guesswork.