pr-lifecycle

Run pre-flight checks and generate a review-ready pull request body.

6|2|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/synaptiai/synapti-marketplace --skill pr-lifecycle-synaptiai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-lifecycle
Source: https://github.com/synaptiai/synapti-marketplace/tree/main/plugins/flow/skills/pr-lifecycle
Command: npx skills add https://github.com/synaptiai/synapti-marketplace --skill pr-lifecycle-synaptiai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many pull requests are opened without clear verification, evidence, or a structured review narrative, which increases reviewer burden and leads to lower-quality merges. This Skill enforces mandatory pre-flight checks, collects verification evidence, and constructs a clear PR body so reviewers can evaluate changes efficiently.

Core Features & Use Cases

  • Pre-flight verification: Runs and aggregates lint, test, and typecheck outputs and ensures the branch is not the default branch and has commits ahead.
  • PR body generation: Produces a structured PR body including summary, changes, comprehension report, requirements adherence table, key decisions, review findings, and verification evidence.
  • Reviewer suggestion & push/create: Suggests reviewers using CODEOWNERS and recent activity, and performs Tier 2 push and PR creation via gh CLI.
  • Use Case: Use this Skill when preparing a feature branch for merge to ensure all quality gates pass, reviewers are appropriate, and the PR documents evidence for decisions.

Quick Start

Run the PR lifecycle skill to verify checks, generate a review-ready PR body with evidence, suggest reviewers, and create the pull request.

Frequently Asked Questions about pr-lifecycle

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

FAQPage Schema
How do I ensure my pull request is review-ready before opening it on GitHub?

To make a pull request review-ready, run pre-flight verification commands for linting and testing, inspect git history, and compose a structured PR body with summary, changes, and verification evidence.

How do I generate a pull request body with verification evidence from my feature branch?

Generating a PR body with verification evidence involves collecting lint, test, and typecheck outputs from your feature branch and formatting them into a structured document with comprehension reports and review findings.

Can I automatically suggest reviewers for a GitHub pull request using CODEOWNERS?

Yes, you can suggest reviewers for a GitHub PR by parsing the CODEOWNERS file and analyzing recent git commit activity to identify appropriate reviewers for the modified files.

What is included in a structured pull request body for code review?

A structured pull request body includes a summary of changes, a comprehension report, a requirements adherence table, key decisions, review findings, and collected verification evidence like lint and test outputs.

Does the PR lifecycle workflow require the gh CLI to create pull requests?

Yes, the PR creation workflow uses the gh CLI to push the feature branch to the remote repository and create the pull request after pre-flight checks and reviewer selection are complete.

Why should I run pre-flight checks before creating a pull request?

Running pre-flight checks before creating a PR ensures the branch is ahead of the default branch, verifies code quality through linting and testing, and reduces reviewer burden by preventing unverified changes from merging.