Results for “xdebug”

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

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

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.

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

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

Systematic root-cause analysis for bugs, errors, and unexpected behavior

Debug issues by investigating logs, database state, and git history

Debugging command. Activates DEBUG mode for systematic problem investigation.

Learn to combine DeFi protocols safely: Uniswap V4 hooks, Aave flash loans, ERC-4626 vaults, Aerodrome on Base, GMX/Pendle on Arbitrum, and dominant DEX per L2.

Enforces a disciplined, evidence-based debugging protocol. Use when the user reports a bug, an unexpected behavior, a broken test, or asks "why is X not working?". Prevents premature fixes and treats symptoms. Blocks code changes until a root cause is confirmed.

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

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.

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

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

Debug Python: pdb REPL + debugpy remote (DAP).

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

debug-logging

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

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

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

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.

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.

Guides systematic root-cause investigation before proposing fixes for any technical issue, with a four-phase process and red flags to avoid guessing.

Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.

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

Debug Python with pdb, breakpoint(), post-mortem inspection, and debugpy remote attach.

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

Debug Python code interactively with pdb and debugpy, covering local breakpoints, post-mortem analysis, and remote attachment to running processes.

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

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Diagnose Apex behavior with debug logs, structured production logging, and async job monitoring, replacing ad-hoc System.debug habits with durable, queryable observability.