Results for “detrack”

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

Trace deprecated shim

Systematically trace bugs backward through call stack to find original trigger

Deploy honeytokens and canarytokens as decoy artifacts to detect intrusions with near-zero false positives.

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.

Deploys deception technology including honeypots, honeytokens, and decoy systems to detect attackers who have bypassed perimeter defenses, providing high-fidelity alerts with near-zero false positive rates.

Tracks DeFi positions across DEX pools, lending markets, and vaults, alerting only on meaningful changes like APR drops, utilization spikes, or health factor approaching liquidation.

Creates a tech sharing deck for internal engineering talks with GitHub-dark theme and JetBrains Mono code blocks.

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

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

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

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

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

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

Systematic debugging with root cause investigation. (gstack)

Autopsy a stuck project, extract salvageable artifacts, and route to a fresh start via $bootstrap-repo reset or new-repo bootstrap

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

User Request

Debugging is the scientific method under time pressure.

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

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

Debugging command. Activates DEBUG mode for systematic problem investigation.

Follow a request end-to-end through the stack from route to database