vibe-continue

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.