shipyard-debugging

Diagnose bugs through root-cause investigation before proposing fixes.

66|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lgbarn/shipyard --skill shipyard-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipyard-debugging
Source: https://github.com/lgbarn/shipyard/tree/main/skills/shipyard-debugging
Command: npx skills add https://github.com/lgbarn/shipyard --skill shipyard-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers resolve bugs and unexpected behavior by enforcing a disciplined, root-cause-driven debugging process before proposing fixes.

Core Features & Use Cases

  • Structured Phase Guidance: Guides Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation to prevent symptom fixes.
  • Diagnostic Instrumentation: Encourages evidence gathering across components to pinpoint failure sources.
  • Educational References: Links to techniques like root-cause tracing and defense-in-depth for robust debugging.

Quick Start

Start debugging by triggering the skill when a bug is detected and proceed through the four phases with documented steps.

Frequently Asked Questions about shipyard-debugging

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

FAQPage Schema
What is systematic debugging and how does root-cause investigation prevent symptom fixes?

Systematic debugging enforces root-cause investigation before proposing fixes to prevent treating symptoms. It uses a four-phase process including pattern analysis and hypothesis testing to pinpoint failure sources across software projects.

How do I debug test failures in CI environments using a structured process?

To debug test failures in CI environments, follow a structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. Use diagnostic instrumentation to gather evidence across components before applying fixes.

What's the best way to trace unexpected behavior back to its source in production systems?

The best way to trace unexpected behavior to its source is using diagnostic instrumentation to gather evidence, followed by backward tracing techniques. This systematic approach enforces evidence collection across components to pinpoint actual failure sources.

Can I use this systematic debugging approach for any software project or is it limited to specific platforms?

You can use this systematic debugging approach for any software project. It is applicable to any bug, error, test failure, or unexpected behavior across all software projects, including production and CI environments.

When should I not use a root-cause driven debugging process?

You should not use a root-cause driven debugging process when you need an immediate patch for a critical symptom without understanding the underlying issue. This systematic approach requires time for pattern analysis and hypothesis testing before implementation.