debugger
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 darrenhinde/openagentscontrol
smart-router-skill
Movie character personality skill with configurable missions - choose your character and watch themed workflows unfold
21context-manager
Context management skill providing discovery, fetching, harvesting, extraction, compression, organization, cleanup, and guided workflows for project context
18task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation
18context7
Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.
11oac-approach
Use before any implementation — understands the request, discovers project context, and proposes a concise plan for user approval before writing any code.
9code-execution
Use when a subtask is ready to implement and has a subtask JSON file with acceptance criteria and deliverables.
9