pr-lifecycle

Coordinate PR lifecycle actions from creation through merge.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill pr-lifecycle-xxih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-lifecycle
Source: https://github.com/xxih/ai-harness-zh/tree/main/packages/github-workflows/targets/codex/skills/pr-lifecycle
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill pr-lifecycle-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当你需要在 PR 生命周期中推进工作时,提供一个统一入口来创建 PR、查看 review 与 checks 状态、处理评审反馈,以及在满足条件时推进合并。

Core Features & Use Cases

  • 统一的原子动作:create、request-review、handle-feedback、check-status、merge
  • PR 上下文感知:base/head、PR URL、review 与 checks 状态、blocker 摘要
  • 指引式决策流:确保在清除 blocker 之前不推进到合并
  • 典型用例:在需要组合动作时执行多步操作,如创建 PR 并请求评审,或在无阻塞时完成合并

Quick Start

请按照当前上下文创建或更新一个 PR,并在需要时发起评审请求,处理反馈,或在无阻塞条件下推进合并。

Frequently Asked Questions about pr-lifecycle

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

FAQPage Schema
How do I automate the pull request lifecycle from creation to merge?

Automating the pull request lifecycle involves coordinating atomic actions like create, request-review, handle-feedback, check-status, and merge. This requires explicit context such as PR URL or head/base, review and checks status, and user approval.

What is a PR lifecycle workflow and when do I need to manage it?

A PR lifecycle workflow guides a pull request from drafting descriptions and requesting reviews to addressing feedback and merging. You need it when combining multiple PR actions into a guided decision flow that ensures blockers are cleared before merging.

Can I merge a pull request when status checks are still failing?

Merging a pull request with failing status checks is blocked by the guided decision flow. The workflow ensures you handle feedback and check status to clear all blockers before approving and executing the final merge action.

What context do I need to provide to create and request a PR review?

To create and request a PR review, you must provide explicit context such as the PR URL or head and base branches. The workflow uses this context to execute atomic actions like drafting descriptions and routing review requests.

What's the best way to handle pull request feedback and check status?

The best way to handle pull request feedback is using a unified entry point to address comments and verify checks status. This guided approach summarizes blockers and prevents progressing to merge until all review feedback is resolved.