Results for “deviations-log”

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

debug-logging

Diagnoses a reported bug, error, test failure, or unexpected behavior through a 4-phase root-cause analysis before any code changes.

Reads and analyzes application logs for debugging and monitoring.

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

Use when a study needs a preregistration or a frozen analysis plan, when confirmatory and exploratory analyses must be separated, or when every deviation from the registered plan must be logged before the result is reported.

changelog-generator

Operations, debugging, and optimization for DAG workflows. Performs root cause analysis on failures, profiles execution performance, aggregates results from parallel branches, bridges context between nodes, and learns patterns from execution history. Activate on "DAG failed", "why did it fail", "root cause", "performance profile", "aggregate results", "merge branches", "execution patterns", "optimize DAG". NOT for planning DAGs (use dag-planner), executing DAGs (use dag-runtime), or validating outputs (use dag-quality).

Analyze Linux system logs including auth.log, syslog, systemd journal, and auditd to reconstruct user activity, detect unauthorized access, and establish event timelines on compromised systems.

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

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

Unified Diary System: A context-preserving automated logger for multi-project development.

Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.

Save the current diagnosis state to disk for cross-session recall, including conclusions, rejected directions, and next steps.

Unified Diary System: A context-preserving automated logger for multi-project development.

LEMON v2.0 — The Degen Fader. Identifies historically reckless traders (DEGEN activity + CHOPPY consistency) on Hyperliquid, monitors their live positions, and counter-trades them when they're bleeding at high leverage. If a cluster of degens goes max-leverage long on a coin and starts losing, LEMON shorts it — betting on their inevitable liquidation cascade. DSL exit managed by plugin runtime via runtime.yaml.

Debugging is the scientific method under time pressure.

Scans modified files for debug leftovers before shipping. Catches console.log, debugger, test URLs, and commented-out code.

OpenTelemetry observability patterns: traces, metrics, logs, context propagation, OTLP export, Collector pipelines, and troubleshooting

Unified Diary System: A context-preserving automated logger for multi-project development.

Failure diagnosis, DAG mutation, and escalation engine for the WinDAGs meta-DAG. Receives failure information and quality vectors from the Evaluator. Classifies failures on four dimensions. Follows a five-level escalation ladder. Applies seven mutation types with saga compensation. Enforces BC-EXEC-002, BC-EXEC-003, BC-FAIL-002, BC-FAIL-005. Activate when operating as the Mutator role in the meta-DAG, when diagnosing node failures, when restructuring a DAG at runtime, or when deciding escalation level.

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