pr-lifecycle

Manage pull request lifecycle from review through CI remediation and user-approved merge.

1|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/softwaresalt/csv-managed --skill pr-lifecycle-softwaresalt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-lifecycle
Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/pr-lifecycle
Command: npx skills add https://github.com/softwaresalt/csv-managed --skill pr-lifecycle-softwaresalt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stalled pull requests by coordinating the end-to-end PR lifecycle, including review feedback handling, CI remediation, and a user-controlled merge gate.

Core Features & Use Cases

  • PR creation and updates: Creates a new PR or refreshes/reuses an existing one for the same branch to avoid duplicates.
  • Review feedback loop: Requests automated review (when supported), monitors review comments, applies bounded fixes, and re-requests review after changes.
  • CI failure remediation: Detects failing CI and delegates remediation to the fix-ci skill using the repository’s CI polling protocol.
  • Non-negotiable merge safety: Runs Copilot review readiness verification (including unresolved thread checks) and requires explicit user approval before merge, never auto-merging.
  • Operational guardrails: Maintains branch context (does not switch to main), performs last-mile re-checks before merge to avoid race conditions, and reports post-merge results without doing checkout-based work.

Quick Start

Use the pr-lifecycle skill to open or update a pull request for your feature branch feature/123-add-indexing and ensure it is ready for user-approved merge after review and CI are clean.

Frequently Asked Questions about pr-lifecycle

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

FAQPage Schema
How do I automate pull request lifecycle management on GitHub?

Automating the pull request lifecycle involves coordinating branch readiness, Copilot review, CI remediation, and user-approved merges. This skill manages that end-to-end workflow by creating or updating PRs, polling for CI health, and enforcing merge gating to prevent stalled PRs.

How do I fix failing CI checks without leaving my pull request workflow?

To fix failing CI checks within your pull request workflow, you can delegate remediation to a dedicated fix-ci skill. This skill detects CI failures, delegates the fix using the repository's polling protocol, and re-requests review after changes are applied.

Does GitHub Copilot review support automated PR merge gating?

GitHub Copilot review supports PR merge gating by verifying review readiness and checking for unresolved threads. This skill enforces non-negotiable merge safety by requiring explicit user approval and performing last-mile re-checks before merging to avoid race conditions.

Can I reuse an existing pull request when updating a feature branch?

You can reuse an existing pull request when updating a feature branch to avoid duplicates. This skill refreshes or reuses existing PRs for the same branch, maintains the branch context without switching to main, and monitors review threads until gates pass.

Why does my automated pull request workflow require explicit user approval before merge?

Automated pull request workflows require explicit user approval before merge to enforce non-negotiable safety gates. This skill never auto-merges, ensuring last-mile verification and unresolved thread checks are completed without race conditions before finalizing the merge.