vibe-sdlc-pr

Monitor PR CI status, triage failures, and apply safe fixes.

6|3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-sdlc-pr
Source: https://github.com/robin-li/vibe-money-book/tree/main/.claude/skills/vibe-sdlc-pr
Command: npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the manual monitoring of CI pipelines for pull requests, triages CI failures, and performs required post-merge housekeeping so PRs do not block progress and project status stays accurate.

Core Features & Use Cases

  • CI Monitoring: Check PR CI status and checks, notify developers when pipelines pass or fail, and surface failure reports for action.
  • Failure Analysis & Remediation: Analyze CI failure logs, distinguish environment issues from code errors, propose or apply safe fixes to open PRs, and re-run CI while ensuring PR state is valid.
  • Post-merge Housekeeping: After merge, sync main, clean merged branches, update 02-Dev_Plan.md and Issue/board status, post completion comments, aggregate status to docs, and support milestone closure workflows.
  • Guardrails & Policies: Enforce rules such as not rebasing or force-pushing dev/main-agent, not merging on behalf of humans, and marking environment failures appropriately.

Quick Start

Monitor the open pull requests, handle CI failures by analyzing logs and applying safe fixes, and update the Dev Plan and Issue status after merges.

Frequently Asked Questions about vibe-sdlc-pr

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

FAQPage Schema
How do I automate GitHub CI monitoring for pull requests?

Automate GitHub CI monitoring by using gh-based checks to read PR CI status and failure logs, then notify developers when pipelines pass or fail. This automates manual monitoring of CI pipelines so PRs do not block progress.

How do I distinguish environment issues from code errors in CI failure logs?

Distinguish environment issues from code errors in CI failure logs by analyzing the logs to categorize the failure source, marking environment failures appropriately, and proposing or applying safe fixes only for code errors. This triage prevents unnecessary changes for environment E2E issues.

What is the best way to automate branch cleanup and Dev Plan updates after a PR merge?

Automate branch cleanup and Dev Plan updates by syncing main, cleaning merged branches, and updating 02-Dev_Plan.md along with Issue and board status. This post-merge housekeeping ensures project status stays accurate without manual intervention.

Can I push safe fixes directly to open pull requests when CI fails?

Yes, you can push safe fixes directly to open PRs when CI fails. The workflow analyzes failure logs, distinguishes environment issues from code errors, and applies safe fixes to the open PR before re-running CI while ensuring the PR state remains valid.

What are the limitations when automating CI fixes and PR merges?

Limitations include enforced guardrails that prevent rebasing or force-pushing dev/main-agent branches, and prohibit merging PRs on behalf of developers. The workflow applies safe fixes only and requires developers to handle the actual merge.

Do I need the Vibe-SDLC workflow to use CI monitoring and post-merge automation?

The CI monitoring and post-merge automation specifically target PRs created during Phase 3 of the Vibe-SDLC workflow where CI gates, E2E issues, branch cleanup, Dev Plan updates, and post-merge verification are required.