vibe-sdlc-pr

Automate CI/CD pipeline operations and post-merge Dev Plan updates.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Katsumitec/Human_First --skill vibe-sdlc-pr-katsumitec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-sdlc-pr
Source: https://github.com/Katsumitec/Human_First/tree/main/projects/ll-ai-first/skills-scripts/vibe-sdlc-skills/vibe-sdlc-pr
Command: npx skills add https://github.com/Katsumitec/Human_First --skill vibe-sdlc-pr-katsumitec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the CI/CD pipeline operations in the Vibe-SDLC Phase 4, automating CI monitoring, failure resolution, and post-merge tasks.

Core Features & Use Cases

  • CI Monitoring: Monitor CI results and identify issues in real-time.
  • Failure Resolution: Assist in resolving CI failures and resubmitting fixes.
  • Post-Merge Tasks: Automate Dev Plan updates and validation reminders post-merge.
  • Use Case: Ideal for development teams following the Vibe-SDLC process, especially in the phase where CI results and post-merge activities are critical.

Quick Start

Invoke the vibe-sdlc-pr skill to monitor CI results for the current PR.

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 CI monitoring and post-merge tasks for pull requests?

Automating CI monitoring and post-merge tasks involves tracking CI check results in real-time, resolving build failures, and automatically updating development plans after a pull request merges. This Skill handles these operations natively within Vibe-SDLC Phase 4 workflows.

Does this CI monitoring automation work with both GitHub and GitLab pipelines?

Yes, this CI monitoring automation is designed for teams using GitHub or GitLab as their version control system. It integrates directly into these platforms to monitor CI results, manage build failures, and execute post-merge operations.

What is the best way to handle CI failures and resubmit fixes automatically?

Handling CI failures automatically requires identifying the failing checks and generating corrective actions. This Skill assists in resolving CI failures by monitoring pipeline results and facilitating the resubmission of fixes during the Vibe-SDLC workflow.

How do I automate Dev Plan updates after a successful pull request merge?

Automating Dev Plan updates after a merge is a post-merge task handled by this Skill. Once the CI pipeline succeeds and the pull request merges, it automatically updates the development plan and sends validation reminders.

Can I use pipeline automation for post-merge tasks without manual intervention?

Yes, you can use pipeline automation to perform post-merge tasks without manual intervention. This Skill streamlines Vibe-SDLC Phase 4 by automatically executing Dev Plan updates and validation reminders once the CI checks pass and the code merges.

Why does CI monitoring require a dedicated Vibe-SDLC Phase 4 workflow?

CI monitoring requires a dedicated Vibe-SDLC Phase 4 workflow because it centralizes the management of CI checks, failure resolutions, and post-merge operations. This structured approach ensures real-time issue identification and consistent development plan updates.