“debugging”

This project focuses on anti debugging techniques written in C++.

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

Systematic troubleshooting using the Scientific Method.

Use when the user is debugging a bug, tracing an error, or asking why something fails.

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven…

Use when the user wants to review or inspect past query executions in Honeydew — what ran, from which client (BI tools, SQL interface, MCP, deep analysis)…

Use for incorrect application behavior whose cause is unknown.

Applies a modified Fagan Inspection methodology to resolve persistent bugs and complex issues.

Find the cause of a defect before proposing a fix - read errors, reproduce, check recent changes, gather evidence from this repo's code map and verification…

Use when diagnosing a failure, flaky behavior, or unexpected output before attempting a fix.

Systematic debugging methodology — binary search isolation, hypothesis-driven debugging, reproducing issues, and root cause analysis.

Codex source debugging: ~/Projects/codex, codex-rs core/tui/exec/cli/app-server/config.

How to debug issues in workstream.

Debug errors, test failures, incorrect output, browser failures, intermittent bugs, and performance regressions through a tight red/green diagnosis loop.

General debugging skill for investigative workflow, error interpretation, and common debugging patterns across languages.

Root-cause a failure with an evidence-first loop (reproduce, one hypothesis, minimal probe, smallest fix, re-run).

Analyze issue text against repository structure to identify likely affected files and debugging directions.

Advanced debugging assistance and error analysis.

Diagnose Fireworks training and deployment issues, including stuck or failed jobs, error messages, poor quality, checkpoint and resume problems, LoRA adapter…

Resolve failures with an evidence-first loop and a verified fix.

Debug failed Konflux e2e test runs by downloading logs and artifacts from GitHub Actions or OpenShift CI (Prow), analyzing test failures, and suggesting fixes.

Diagnose PostHog Surveys configuration and responses across all five SDKs (web/posthog-js, iOS, Android, Flutter, React Native).

Systematic debugging methodology, language-specific debuggers, and common scenario playbooks.

Use when debugging and needing falsifiable hypotheses, alternative explanations, or stronger root-cause discipline