One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill debugger-picmakpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/reference/content/methodology/templates/skills/debugger
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill debugger-picmakpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents random debugging and unreliable patches by requiring systematic investigation of the root cause before implementation, followed by evidence-based verification and documentation.

Core Features & Use Cases

  • Four-Phase Debugging: Reproduce the issue, identify the root cause, test focused hypotheses, and implement a verified fix.
  • Documentation Research: Investigate framework, dependency, native, OS, and SDK issues before empirical troubleshooting when applicable.
  • Evidence-Based Verification: Require focused tests, regression checks, and documentation in BLOCKERS.md or LEARNINGS.md when appropriate.
  • Use Case: When an unexplained test failure or regression occurs, trace the data flow, compare working and broken implementations, test one hypothesis at a time, and record the confirmed cause and prevention steps.

Quick Start

Ask the debugger skill to investigate the failing test, identify its root cause, implement one targeted fix, and verify the complete test suite.

Frequently Asked Questions about debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to find the root cause of a failing test or software regression?

To find the root cause of a failing test or software regression, systematically reproduce the issue, trace data flow, compare working and broken implementations, and test one focused hypothesis at a time before applying a fix.

How do I fix production bugs without applying random patches?

To fix production bugs without random patches, follow a four-phase debugging process: reproduce the evidence, identify the root cause, test focused hypotheses targeting the specific failure, and implement a verified fix with regression checks.

Can I use systematic debugging for build failures and integration problems involving dependencies?

Yes, systematic debugging applies to build failures and integration problems involving dependencies, frameworks, or native systems by requiring documentation research and reproducible evidence before empirical troubleshooting and applying fixes.

How do I verify a software fix and prevent future regressions?

To verify a software fix and prevent future regressions, run focused tests to confirm the resolution, perform regression verification on the complete test suite, and document the confirmed cause and prevention steps in LEARNINGS.md.

When should I escalate unresolved test failures or repeated failed fixes?

You should escalate unresolved test failures or repeated failed fixes after systematic hypothesis testing fails to identify the root cause, ensuring that blocker documentation is recorded to facilitate further investigation.