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

Easy debugging skill pack for Content Factory. Use when the user says debug skills, @debug-skills, something is broken, failed pipeline, or bug pack. Auto-loads systematic-debugging, cf-orchestrator, debugging-loop, and bug-fixing workflow.

Debugging command. Activates DEBUG mode for systematic problem investigation.

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

Captures and analyzes Windows debug output (OutputDebugString, DbgPrint/KdPrint) from the command line, with filtering, bounded execution, and remote monitoring.

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.

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.

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"

Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

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

Step-by-step debugging workflow: reproduce the bug, isolate the failing component, trace to root cause, apply a targeted fix, and verify the fix resolves the issue without regressions. Use when you encounter a bug, error, exception, crash, or unexpected behavior that needs troubleshooting.

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.

Run a reproduce → isolate → verify debugging workflow for concrete bugs, regressions, flaky failures, and environment-specific behavior. Use when the user already has a failing command, test, request, UI flow, or narrowed symptom and needs root-cause diagnosis or fix verification rather than raw log-line selection, broad test-policy design, PR review, or generic performance tuning.

Diagnose and observe an Oxla distributed analytical database using system catalog tables, Prometheus metrics, runtime log-level changes, and troubleshooting workflows for slow queries, node health, and memory/OOM pressure. Also covers debugging Oxla's external data sources, including the Redpanda/Kafka ingestion path.

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.

Investigates slow responses, tool failures, and guardrail rejections by querying agent trace logs and performance metrics.

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