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 aplaceforallmystuff/minervia-starter-kit
start-project
Create a new project with proper PARA structure. Ensures consistent project setup with completion criteria and status tracking.
3think-first
Apply mental models before major decisions. Enforces structured thinking before implementation.
3antislop
Detect AI-generated writing patterns (slop). Scans for banned phrases, structural tells, and scoring.
2lessons-learned
Structured retrospective for incidents and mistakes. Transforms problems into systematic improvements.
2extract-wisdom
Dynamic wisdom extraction that adapts sections to content. Use when analyzing YouTube videos, podcasts, interviews, articles, or any content where you want to capture the best insights.
2minervia-restore
List and restore from Minervia backups. Shows available backup timestamps and lets you restore files to previous versions. Use when you need to undo an update or recover customizations.
2