skills.rest
daudaudinang
daudaudinangCOMMUNITY
Explore all skills by this author →
GitHub

vibecode-doctor

Validate Vibecode runtime health and report READY or DEGRADED status.

Updated Apr 14, 2026
Search Tags:#runtime#diagnostics#canonical#doctor#vibecode#gitnexus
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill vibecode-doctor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibecode-doctor
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/vibecode-doctor
Command: npx skills add https://github.com/daudaudinang/vibecode --skill vibecode-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vibecode Doctor provides a centralized health check for your Vibecode workspace, validating the canonical runtime root, presence of legacy mirrors, active runtime state DB, script availability, and readiness of the GitNexus CLI/index.

Core Features & Use Cases

  • Health posture: verifies canonical paths from configuration and detects missing or misaligned runtime artifacts.
  • Preflight readiness: helps triage issues before starting major flows like plan, implement, or debug-investigator.
  • Guided bootstrap: reports READY or DEGRADED status and points to bootstrap actions when problems are detected.
  • Diagnostic outputs: surfaces actionable signals to fix path or mirror problems quickly.

Quick Start

Run from the project root: python .codex/scripts/vibecode_doctor.py to generate a health report.

Frequently Asked Questions about vibecode-doctor

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

FAQPage Schema
How do I diagnose Vibecode runtime health before starting a major workflow?▼

Diagnose Vibecode runtime health by running a script that validates the canonical root, legacy mirrors, active state DB, and GitNexus CLI readiness, reporting READY or DEGRADED status to fix path issues quickly.

What is runtime path drift and how do I check for it in my workspace?▼

Runtime path drift occurs when expected workspace artifacts are missing or misaligned. You can check for it by validating the canonical runtime root from configuration files and detecting missing legacy mirrors or state DB paths.

How do I verify if the GitNexus CLI and required scripts are available?▼

Verify GitNexus CLI availability by running a diagnostic check that confirms the CLI and required LP scripts like state_manager.py, lp_pipeline.py, and validate_contract.py are present and ready in your workspace.

Do I need to fix a DEGRADED runtime status before running plan or implement workflows?▼

Yes, you should fix a DEGRADED runtime status before launching major workflows like plan, implement, or debug-investigator to ensure tool-call reliability and prevent runtime path drift from causing failures.

How do I troubleshoot tool-call reliability issues in my runtime environment?▼

Troubleshoot tool-call reliability by running a preflight readiness check that validates the canonical runtime root, active state DB, and GitNexus index, surfacing actionable diagnostic signals to resolve misaligned configurations.

What does a workspace health check validate in a Vibecode environment?▼

A workspace health check validates the canonical runtime root from config.toml, checks for legacy mirrors like .agents and .codex, confirms the active state DB path, and ensures the GitNexus CLI is ready.

Related Skills

Explore More Software Engineering Skills→
julianobarbosajulianobarbosa
7

Iterm2

Manage iTerm2 and tmux workflows with native -CC integration.

Community
Intermediate
rampstackcorampstackco
523

launch-runbook

Plan and execute structured launch runbooks with rollback procedures.

Official
Advanced
adamaltmejdadamaltmejd
2

build-db

Orchestrate Registry Research Toolkit database rebuilds with integrity validation and dbdiff analysis.

Community
Advanced
ihj04982ihj04982

put-interaction-logic-in-event-handlers

Move React interaction logic directly into event handlers.

Community
Basic