vibe-debug-serve

Diagnose vibe3 serve orchestration issues by analyzing logs and tracing execution paths.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-debug-serve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-debug-serve
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-debug-serve
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-debug-serve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

vibe3 serve debugging can be complex; this skill provides a structured workflow to collect logs, inspect execution traces, and diagnose governance and manager chain failures without risking production state.

Core Features & Use Cases

  • Guided log and event analysis for vibe3 serve heartbeat, dispatch, and governance.
  • Step-by-step debugging flow to isolate issues across global serve and per-flow tasks.
  • Safe validation with dry-run checks and isolated branches to minimize impact on running systems.

Quick Start

Launch a minimal diagnostic pass to begin debugging the current vibe3 serve session and collect essential logs.

Frequently Asked Questions about vibe-debug-serve

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

FAQPage Schema
How do I debug vibe3 serve orchestration failures?

Trace vibe3 serve execution paths by analyzing logs in the temp/logs directory. This guided debugging workflow inspects heartbeat, dispatch, and governance interactions to diagnose per-flow issues while maintaining minimal impact on running systems.

Can I troubleshoot vibe3 governance and manager chain issues without affecting production?

Troubleshoot vibe3 governance and manager chain issues safely using dry-run checks and isolated branches. This procedure requires explicit validation before applying any changes, ensuring minimal impact on your running orchestration systems.

What is the best way to diagnose vibe3 serve heartbeat and dispatch errors?

Diagnose vibe3 serve heartbeat and dispatch errors through a step-by-step guided log analysis. The workflow collects relevant logs and traces execution paths to pinpoint failures across the serve orchestration manager interactions.

Does vibe3 serve debugging support safe validation before applying fixes?

Vibe3 serve debugging supports safe validation by enforcing dry-run checks, branch isolation, and explicit validation before applying fixes. This minimal-change procedure ensures you can diagnose and guide fixes without risking production state.

Why does vibe3 serve orchestration fail across global serve and per-flow tasks?

Vibe3 serve orchestration fails across global serve and per-flow tasks due to issues in heartbeat, dispatch, governance, or manager interactions. Analyzing logs and tracing execution paths in temp/logs isolates the specific failure point.