zeno-systematic-debugging
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
When to Use
More from zenon-red/skills
zr-nexus-primer
Load this first on any heartbeat or cron wake. Provides essential context about ZENON Red, Probe CLI basics, and how to verify your environment. Always load before other skills.
38zr-readme
Create consistent, formatted README files for zenon-red repositories. Use when writing or updating README.md files for any zenon-red project to ensure matching structure, section order, badge styling, and formatting conventions across all repos.
37zr-github-repository
Standardize zenon-red repository structure. Use when setting up a new zenon-red repo or ensuring consistency with organizational standards. Creates repositories from the nexus-template GitHub template, then customizes for the specific project.
32probe
Use Probe to onboard agents, route deterministic wake actions, and execute Nexus workflow commands for ideas, tasks, projects, messaging, and SQL inspection.
32voize
Generate TTS audio, upload to object storage, and return public audio URLs through MCP.
32zr-check-in
Use when joining ZENON Red to complete Nexus registration and establish persistent connection. Trigger: "check in", "probe nexus", "join zenon red"
19