vibe-done

Close terminal PR issues and append handoff entries via GitHub CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a guarded, auditable finalization workflow for human-AI collaboration flows so teams can confirm terminal PR outcomes, close owned issues, and record a clear handoff without altering source code or local truth stores.

Core Features & Use Cases

  • Flow validation: Verify the flow and PR are in a terminal state before proceeding.
  • Issue closure: Close the primary or explicitly owned repository issues using the appropriate CLI tools.
  • Handoff & audit: Append a terminal handoff entry and run minimal consistency checks to preserve an auditable trail.
  • Feedback capture: Extract issues found from handoff records and create or update follow-up issues for medium-or-higher severity items.
  • Use case: When a feature branch PR is merged, run this skill to close the related issue, write a completion milestone to the handoff, and post any necessary feedback issues.

Quick Start

Run the vibe-done skill to validate the terminal PR state, close the primary issue, append a terminal handoff entry, and perform a minimal consistency audit.

Frequently Asked Questions about vibe-done

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

FAQPage Schema
How do I close GitHub issues automatically after a pull request is merged?

To close GitHub issues after a pull request merge, this skill validates the terminal PR state and closes owned issues via GitHub CLI, producing an auditable flow closure without modifying source code.

What is the best way to record a handoff after a feature branch reaches a terminal state?

Recording a handoff after a terminal PR state involves appending terminal handoff entries using vibe3 handoff commands and running minimal consistency checks to preserve an auditable collaboration trail.

Can I extract feedback from handoff records to create follow-up GitHub issues?

Yes, extracting feedback from handoff records creates follow-up GitHub issues; this skill identifies medium-or-higher severity items from the handoff and creates or updates issues to track them.

Does the issue closeout process modify local truth files or source code?

No, the issue closeout process does not modify local truth files or source code; it performs issue closure via GitHub CLI and appends handoff entries while running a minimal consistency check.

When do I need to run an auditable finalization workflow for a pull request?

You need an auditable finalization workflow when a local collaboration flow or feature branch has reached a terminal PR state and requires issue closeout, handoff recording, and feedback extraction.