vibe-check

Audit and repair vibe3 task and flow synchronization issues using shell APIs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a safe, observable process to detect and remediate mismatches between vibe3 task runtime bindings and flow state, preventing stale runtime bindings and broken auto-task worktrees from disrupting local development scenes.

Core Features & Use Cases

  • Runtime audit: Run and interpret vibe3 shell inspection outputs to summarize active, ready, blocked, and stale task/flow bindings.
  • Deterministic recovery: Where the shell exposes atomic commands and the fix is unambiguous, execute shell-based recovery such as resuming auto-created tasks or unbinding stale runtime references.
  • Guardrails and reporting: Avoid direct JSON/SQLite edits, require user confirmation for ambiguous operations, and produce a clear audit report of commands run and verification results.
  • Use case: When a completed task still holds a runtime binding or a runtime points to a missing worktree, use this skill to classify the issue, apply safe shell fixes if unique, or present evidence and options for user approval.

Quick Start

Ask the assistant to audit the current vibe3 runtime scene, list discrepancies between task and flow status, and execute safe shell repairs only for issues that are deterministic.

Frequently Asked Questions about vibe-check

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

FAQPage Schema
How do I audit vibe3 task runtime bindings and flow status?

You can repair stale vibe3 runtime bindings by executing deterministic shell-based recovery commands, such as resuming auto-created tasks or unbinding stale runtime references. Direct JSON or SQLite edits are avoided to ensure safe, observable remediation.

Why does a completed vibe3 task still hold a runtime binding?

A completed vibe3 task holding a runtime binding indicates a synchronization issue between the task and flow state. The skill detects this mismatch during the runtime audit and classifies it for safe shell-based recovery or user-approved rollback.

Can I use shell APIs to recover an auto-created vibe3 worktree pointing to a missing path?

Yes, you can use shell APIs to recover auto-created vibe3 worktrees pointing to missing paths. When the shell exposes atomic commands and the fix is unambiguous, the skill executes deterministic recovery; otherwise, it prompts for user confirmation with evidence.

What's the best way to verify vibe3 flow status and prevent broken auto-task worktrees?

The best way to verify vibe3 flow status and prevent broken auto-task worktrees is to run a runtime audit that reads shell inspection outputs. It produces a concise audit report listing commands executed and verification results for observable remediation.

Are direct database edits supported for fixing vibe3 runtime state?

No, direct JSON or SQLite edits are not supported for fixing vibe3 runtime state. The skill enforces guardrails by using only shell APIs for deterministic fixes and requires user confirmation for ambiguous operations to maintain safety.