debug-orchestration

Name: debug-orchestration
Availability: InStock
Author: shynlee04

Coordinate debugging lifecycles for AI coding sessions from detection to documentation.

51|17|Updated Feb 10, 2026

Search Tags:#automation #testing #debugging #error handling #orchestration #lsp

Ready to run

npx skills add https://github.com/shynlee04/hivemind-plugin --skill debug-orchestration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-orchestration
Source: https://github.com/shynlee04/hivemind-plugin/tree/main/skills/debug-orchestration
Command: npx skills add https://github.com/shynlee04/hivemind-plugin --skill debug-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust framework for managing complex debugging processes, ensuring systematic investigation, context preservation, and efficient resolution of issues.

Core Features & Use Cases

Unified Debugging: Integrates event detection (LSP, tests, runtime errors) with context preservation and strategy selection.
Orchestration Framework: Guides the AI through a multi-layered debugging process, from event capture to resolution and documentation.
Use Case: When a test fails or LSP reports an error, this Skill automatically triggers a debugging session, preserves the current state, selects the best debugging strategy (systematic or parallel), executes the debug loop, verifies the fix, and documents the solution.

Quick Start

Activate the debug orchestration skill to investigate the latest test failure.

Frequently Asked Questions about debug-orchestration

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

FAQPage Schema

How do I orchestrate systematic debugging workflows for AI coding sessions?▼

Systematic debugging workflows coordinate a comprehensive lifecycle by detecting events from LSP diagnostics, test failures, and runtime errors, then preserving context and executing resolution strategies.

What is the best way to automate debugging when tests fail or LSP reports errors?▼

Automating debugging triggers a session upon test failures or LSP errors, preserving current state, selecting systematic or parallel strategies, verifying fixes, and documenting solutions.

How does context preservation work during a debugging lifecycle?▼

Context preservation during a debugging lifecycle captures the current session state before strategy execution, ensuring systematic investigation and hypothesis testing proceed without losing prior work history.

Can I manually invoke a debugging session instead of waiting for runtime errors?▼

Manual invocation initiates debugging orchestration immediately, bypassing automatic event detection to run hypothesis testing, solution verification, and documentation on demand.

Do I need specific dependencies to run systematic debugging workflows?▼

No dependencies are required to run systematic debugging workflows; the orchestration framework operates independently to manage event detection and strategy execution.

When should I not use an orchestration framework for debugging?▼

Avoid using orchestration frameworks for trivial syntax fixes or single-line corrections where automated event detection and multi-layer strategy execution add unnecessary overhead.