vibe-continue

Inspect git and vibe3 state to reconcile development flow context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restore and reconcile the active development flow context when returning to a branch or task so collaborators can safely continue work without relying on inconsistent local state or inventing unverified fixes. It enforces the principle of prioritizing shared truth sources and treating local handoff notes as supplementary context that must be validated. The Skill guides the user through reading authoritative signals and producing a clear next action without performing unsafe changes.

Core Features & Use Cases

  • Shared-truth-first restoration: Read shared flow state before local handoff to determine the authoritative task context.
  • Deterministic fact-gathering: Collect git branch, working tree cleanliness, PR facts, vibe3 flow and task status, and local handoff notes to produce a coherent view.
  • Clear continuation advice: Generate concise suggested next steps prioritizing plan paths, next_step entries, or annotated handoff clues when appropriate.
  • Use case: A developer returning to a paused feature branch can quickly reconcile the remote flow state, local handoff, and git facts to pick up work without creating merge or process confusion.

Quick Start

Resume the current development flow by reading git status, vibe3 flow show, vibe3 task status --all --check, and vibe3 handoff show, then produce a concise suggested next action.

Frequently Asked Questions about vibe-continue

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

FAQPage Schema
How do I resume a paused git feature branch without losing context?

To resume a paused git feature branch, read shared flow state, local handoff notes, and git status to reconcile the context. The skill cross-checks these sources to output a concise next action without performing unsafe changes.

What is shared truth prioritization in development flow handoff?

Shared truth prioritization means reading authoritative remote flow state before local handoff notes. It ensures contributors validate local clues against shared project signals to avoid merge or process confusion when continuing work.

How do I reconcile local handoff notes with vibe3 flow state?

Reconcile local handoff notes with vibe3 flow state by running read-only inspections of vibe3 flow show, task status, and handoff records. The skill cross-checks inconsistencies and prioritizes shared truth over local notes.

Does the vibe-continue skill modify my git branch or working tree?

No, vibe-continue does not modify your git branch or working tree. It performs read-only inspections of git and vibe3 outputs to generate actionable recommendations without invoking unverified repair commands.

What should I do if local handoff notes conflict with the remote task status?

If local handoff notes conflict with remote task status, prioritize the shared truth sources. The skill cross-checks these inconsistencies and generates suggested next steps based on plan paths and annotated handoff clues.