beo-debugging

Apply a triage-reproduce-diagnose-fix sequence to resolve Beo bead blockers.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-debugging
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/debugging
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflow for identifying, triaging, and resolving blockers, failures, and runtime issues in Beo beads.

Core Features & Use Cases

  • Structured triage: classify builds, tests, runtimes, and integrations before investigation.
  • Reproducible debugging: isolate minimal reproduction steps and capture exact outputs for reliable fixes.
  • Knowledge-store integration: consult .beads/critical-patterns.md and references/diagnostic-checklist.md to leverage known patterns and checks.

Quick Start

Execute the debugging sequence on a failing bead to produce a documented root cause and verified fix.

Frequently Asked Questions about beo-debugging

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

FAQPage Schema
How do I debug failing Beo beads in my AI workflow?

Debug failing Beo beads by applying a structured triage-reproduce-diagnose-fix sequence that isolates minimal reproduction steps and produces a verified fix plan with debug notes.

What is the best way to triage runtime and integration failures in Beo beads?

Triage Beo bead failures by classifying builds, tests, runtimes, and integrations before investigation, ensuring a structured approach to isolating root causes and capturing exact outputs.

How do I reproduce a blocker in a Beo bead workflow?

Reproduce a blocker in Beo beads by isolating minimal reproduction steps and capturing exact outputs, enabling reliable fixes and a documented root cause for the failure.

Does Beo debugging consult known failure patterns to avoid repeating issues?

Yes, Beo debugging consults `.beads/critical-patterns.md` and `references/diagnostic-checklist.md` to leverage known patterns and checks, avoiding repeated problems during the fix sequence.

Do I need a diagnostic checklist to fix build and test failures in Beo beads?

Yes, consulting a diagnostic checklist is required to produce a verifiable, reproducible fix plan with debug notes when resolving build, test, runtime, and integration issues.

When should I use systematic debugging for blocked AI-bead workers?

Use systematic debugging for blocked AI-bead workers when you need to methodically resolve blockers and failures across build, test, runtime, and integration environments with a documented root cause.