debug

Reproduce bugs deterministically and guide teams through structured four-phase triage workflows.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill debug-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/leocosta/octopus/tree/main/skills/debug
Command: npx skills add https://github.com/leocosta/octopus --skill debug-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce bugs deterministically and guide teams through a structured, four-phase triage and fix workflow.

Core Features & Use Cases

  • Deterministic reproduction: establish a reproducible bug scenario with minimal context.
  • Phase-driven remediation: isolate, fix with a regression test, and document root cause.
  • Collaboration and governance: pairs with implement and audit-all to ensure safe, auditable changes.

Quick Start

Invoke the bug-triage workflow on a reproducible issue with /octopus:debug <bug> to start the four-phase loop.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I reproduce a bug deterministically from a minimal bug report?

Deterministic bug triage uses a four-phase workflow to reproduce, isolate, fix, and document runtime failures. It ensures safe remediation by requiring regression tests and artifacting at each phase, allowing teams to systematically resolve codebase issues with auditable traceability.

What's the best way to structure a bug triage workflow for my codebase?

Structured bug triage pairs with implement and audit-all components to ensure safe, auditable codebase changes. These complementary tools enforce regression testing and artifacting during the remediation workflow, guaranteeing that fixes are verified and future agents can reproduce and learn from the process.

Why do I need regression testing when applying a bug fix?

The four-phase triage workflow requires deterministic reproduction, isolation, regression testing, and documentation to resolve bugs. It specifies requirements for each phase and artifacting, ensuring future agents can reproduce and learn from the structured remediation process across codebases and runtime failures.

How does artifacting improve the bug isolation process?

Artifacting during bug isolation captures the deterministic reproduction steps and root cause documentation for future agents. By preserving these artifacts within the triage workflow, teams create a knowledge base that enables future agents to reproduce and learn from past runtime failures and codebase regressions.