“debugging”

Use for systematic debugging.

Stack-specific debugging (Python/async/pdb, logs, stack traces) when root cause is unclear.

Systematically debug an error or unexpected behavior.

Systematic debugging workflow for isolating and fixing bugs

Use when the user says 'diagnose', 'debug this', reports something broken/throwing/failing/slow, when encountering a bug/test failure/unexpected behavior and…

Debug issues systematically.

Systematic bug investigation with hypothesis tracking

Use when Malvex needs debugger-backed runtime evidence such as breakpoints, arguments, registers, threads, heap state, or decrypted configuration.

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

Use when something is failing, regressing, or behaving unexpectedly and the goal is root-cause analysis, narrowest fix, and verification.

Systematic root-cause isolation and minimal fix proposal for software bugs.

Use for runtime bugs: crashes, wrong output, intermittent or silent failures, flaky tests, code that works locally but not in prod.

Use for any bug, test failure or unexpected behavior, before proposing a fix - reproduce, find the root cause, one hypothesis at a time.

When there is a bug, error, failed test, regression, performance drop, unexpected result, or anomalous data, establish a tight feedback loop and find the root…

Find the root cause of a defect or a symptom by first building a feedback loop that shows the failure on demand, recording the behaviour that must not change…

Use when diagnosing a bug, error, crash, or unexpected behavior.

Diagnose failures from evidence and make the smallest safe correction.

The house debugging discipline for a bug or unexpected behaviour: reproduce it on demand, form one testable hypothesis, isolate the cause with evidence…

Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running…

Codex debugging: codex-rs core/tui/exec/cli/app-server/config.

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines.

[ARCHIVED v0.1.0 — superseded by build-loop:debug-loop] Older source-tracked copy of the iterative debug loop, retained for version history.

Guide for debugging issue on a specific code sections, pattern, or files.