skills.rest
jacobcy
jacobcyCOMMUNITY
Explore all skills by this author →
GitHub

vibe-integrate

Assesses GitHub pull requests for merge readiness via CI, reviews, LOC thresholds, and sequencing.

6|Updated Feb 5, 2026
Search Tags:#merge#handoff#code-review#ci#pull-request#dead-code#loc
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-integrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-integrate
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-integrate
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-integrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces uncertainty and manual effort in taking pull requests from "opened" to "merged" by systematically checking CI status, review evidence, size governance, and merge order so teams can merge with confidence and maintain repository quality.

Core Features & Use Cases

  • CI and Review Verification: Inspect CI checks, review decisions, and unresolved review threads to determine merge readiness.
  • Stacked PR Sequencing: Identify stacked pull request relationships and enforce correct merge order to avoid conflicts.
  • LOC and Quality Gates: Run size threshold checks and dead-code audits against repository thresholds and create follow-up issues or exceptions when appropriate.
  • Handoff and Traceability: Append structured handoff entries, create cleanup issues when needed, and record exceptions into configuration to preserve governance.
  • Use Case: When a feature branch has multiple dependent PRs, use this Skill to validate CI, gather review evidence, run LOC audits, merge in order, and append the final handoff.

Quick Start

Assess PR 123 by checking CI results, verifying review evidence and LOC thresholds, resolving or recording blockers, and then merge or append the handoff entry.

Frequently Asked Questions about vibe-integrate

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

FAQPage Schema
How do I safely assess and merge GitHub pull requests with CI checks?▼

To safely merge pull requests, assess CI status, verify review evidence, check LOC thresholds, and resolve unresolved review threads before advancing to merge readiness.

What is the correct merge sequence for stacked pull requests?▼

Stacked pull requests require strict merge sequencing to avoid conflicts. Identify dependent PR relationships and enforce the correct merge order before integrating the base branch.

How do I enforce LOC thresholds and dead-code audits before merging?▼

Enforce LOC thresholds and dead-code audits by running checks against config/settings.yaml. Create follow-up cleanup issues or record exceptions into configuration to preserve governance.

Can I merge configuration and documentation changes with unresolved review threads?▼

Configuration and documentation changes require resolving unresolved review threads. The merge readiness process inspects review decisions and blocks merges until threads are resolved.

How do I record handoff entries after merging a feature branch?▼

Record handoff entries by appending structured handoff logs after completing CI verification, review evidence checks, and LOC audits to maintain repository traceability and quality.

Related Skills

Explore More Software Engineering Skills→
Arry8Arry8
1

github-pr-ready-check

Assess GitHub pull request readiness using gh CLI data.

Community
Intermediate
AnjinMeiliAnjinMeili

context-keeper

Record and restore project context across sessions using four persistent markdown registers.

Community
Intermediate
zaiyemeiyou404zaiyemeiyou404

requesting-code-review

Automate code review with pre-commit security scans and quality checks.

Community
Advanced
bhianerdbhianerd
1

land-and-deploy

Merge eligible GitHub pull requests after CI and readiness checks, then verify deployment and canary health.

Community
Advanced