Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Systematic Debugging
## Overview
**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
Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues
**Use this ESPECIALLY when:**
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue
**Don't skip when:**
- Issue seems simple (simple bugs have root causes too)
- You're in a hurry (rushing guarantees rework)
- Manager wants it fixed NOW (systematic is faster than thrashing)
## The Four Phases
You MUST complete each phase before proceeding to the next.
### Phase 1: Root Cause Investigation
**BEFORE attempting ANY fix:**
1. **Read Error Messages Carefully**
- Don't skip past errors or warnings
…
The line at the top of this page pins the label git:20261006.308cb43, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_5p5df3mhhxsvwewm
GET https://markdownregistry.com/api/v1/resolve?ref=joahanmorales/upiixia-agentic-kit/systematic-debugging
GET https://markdownregistry.com/api/v1/blob/df3f6451b43f4b5115b4599e17ece202fe8d8283f1ff5a40a6584ad2e44710fe
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/design-taste-frontend/SKILL.md · Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/karpathy-guidelines/SKILL.md · Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/mcp-builder/SKILL.md · Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/redesign-existing-projects/SKILL.md · Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/vercel-react-best-practices/SKILL.md · React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
joahanmorales/upiixia-agentic-kit · kit/.uak/skills/webapp-testing/SKILL.md · Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend…
joahanmorales/upiixia-agentic-kit · kit/.uak/stacks/ai-agent/skills/stack-ai-agent/SKILL.md · Conventions for the AI agent stack (MCP tools per task, eval cases per tool, offline evals in the gate). Use when…
joahanmorales/upiixia-agentic-kit · kit/.uak/stacks/django/skills/stack-django/SKILL.md · Conventions for the Django stack (one app per task, auto-included urls, pytest-django, migrations through a human). Use…
mvschwarz/openrig · skills/_canonical/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
cbrock84/headcount · plugins/technology/skills/systematic-debugging/SKILL.md · Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever…
a5c-ai/babysitter · library/methodologies/superpowers/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause…
