Results for “defect-detection”

Pattern-Based Diagnosis

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.

Diagnose failures from runtime evidence before editing code.

Guides developers through capturing diagnostic artifacts to diagnose production .NET performance issues, including tool selection and data collection across Windows, Linux, containers, and Kubernetes.

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".

Provides a structured debugging workflow for diagnosing 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.

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

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

Reproduce a bug as a failing regression test, fix until green, review, and commit via a delegated pipeline.

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.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

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

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

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.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Diagnoses a reported bug, error, test failure, or unexpected behavior through a 4-phase root-cause analysis before any code changes.

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

Debug application issues with techniques for Python, JavaScript, performance profiling, production incidents, and network problems.

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

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

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

Runs a disciplined diagnosis loop for hard bugs and performance regressions, from reproduction through hypothesis testing, instrumentation, fixing, and regression testing.

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

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Reproduces failures, gathers evidence, tests hypotheses, fixes root causes, and adds regression coverage.

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

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.

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

Debugging command. Activates DEBUG mode for systematic problem investigation.

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)