skills.rest
tuvens
tuvensCOMMUNITY
Explore all skills by this author →
GitHub

reviewing-a-phase-pr

Validate phase pull requests for merge readiness using review checklists.

Updated Aug 27, 2026
Search Tags:#release management#code review#pull request#github#regression testing#merge gate#phase review
One-click install
npx skills add https://github.com/tuvens/phased-development --skill reviewing-a-phase-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-a-phase-pr
Source: https://github.com/tuvens/phased-development/tree/main/skills/reviewing-a-phase-pr
Command: npx skills add https://github.com/tuvens/phased-development --skill reviewing-a-phase-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps a VP of Engineering evaluate whether a phase pull request is ready to merge by applying the phased-development review gate and collecting the evidence needed for a safe decision.

Core Features & Use Cases

  • Phase PR validation: Checks PR metadata, mergeability, closes references, and target branch alignment.
  • Regression and smoke coverage: Verifies regression guides, prior-phase smoke tests, and cumulative regression expectations.
  • Review hygiene checks: Confirms automated review comments are resolved, issue labels are correct, and optional style or Chrome evidence is present.
  • Use case: Use this Skill when someone asks whether PR #123 is ready to merge, or when a formal phase PR review is needed before approving release progress.

Quick Start

Review PR #123 using the phase PR checklist and return blockers, recommendations, and a final verdict.

Frequently Asked Questions about reviewing-a-phase-pr

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

FAQPage Schema
How do I verify a phase pull request is ready to merge?▼

To verify a phase pull request is ready to merge, you need to check PR metadata, regression guides, prior-phase smoke tests, and automated review comments to ensure all release criteria are satisfied.

What is a phase PR review in a cascade development model?▼

A phase PR review in a cascade development model is a merge gate evaluation where a VP of Engineering validates phase integration, checks issue labels, and reviews Chrome MCP evidence before approving release progress.

How do I check pull request mergeability and regression coverage before approving?▼

Checking pull request mergeability and regression coverage involves validating target branch alignment, confirming cumulative regression expectations, and ensuring prior-phase smoke tests pass before giving a final merge verdict.

Does this phase PR review workflow verify automated review comments and issue labels?▼

Yes, this phase PR review workflow verifies automated review comments are resolved, confirms issue labels are correct, and checks for optional style reuse notes or Chrome MCP evidence to ensure review hygiene.

Can I use this to assess an ambient request to merge a phase PR?▼

Yes, you can use this to assess an ambient request to merge a phase PR, as it supports epic-direct-to-main integration reviews and evaluates whether a PR meets the phased-development review gate criteria.

What is checked during a phase PR validation for release management?▼

During phase PR validation for release management, the system checks PR metadata, closes references, target branch alignment, regression guides, and automated review comments to return blockers, recommendations, and a final verdict.

Related Skills

Explore More Software Engineering Skills→
monoesmonoes
15

github-issue-triage

Categorize, rank, and recommend actions for GitHub issues.

Official
Advanced
Awannaphasch2016Awannaphasch2016

code-review

Automate code review for security, performance, and quality issues.

Community
Advanced
LeKayLeKay

smoke-check

Execute automated and manual smoke tests in CI/CD pipelines.

Community
Advanced
mrkingsleyobimrkingsleyobi

github-code-review

Coordinate multi-agent code reviews for GitHub pull requests.

Community
Advanced