pr-lifecycle

Standardize Pull Request creation, local CI validation, and review handling.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/UtakataKyosui/C2Lab --skill pr-lifecycle-utakatakyosui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-lifecycle
Source: https://github.com/UtakataKyosui/C2Lab/tree/main/plugins/pr-lifecycle/skills/pr-lifecycle
Command: npx skills add https://github.com/UtakataKyosui/C2Lab --skill pr-lifecycle-utakatakyosui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the entire Pull Request (PR) lifecycle, from creation and local CI validation to review handling and merge preparation, ensuring consistency and efficiency.

Core Features & Use Cases

  • Standardized PR Process: Guides users through creating, validating, and preparing PRs for merging.
  • Local CI Validation: Ensures code passes checks like linting and formatting before pushing.
  • Review Management: Integrates with review-workflow for handling comments and verification.
  • Pre-Merge Checklist: Provides a clear checklist to confirm readiness for merging.
  • Use Case: When you've finished implementing a feature, use this skill to run all relevant CI checks locally, create a well-formatted PR, and ensure all review comments are addressed before merging.

Quick Start

Use the pr-lifecycle skill to perform a pre-push CI check for your current changes.

Frequently Asked Questions about pr-lifecycle

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

FAQPage Schema
How do I standardize the Pull Request lifecycle from creation to merging?

Standardizing the Pull Request lifecycle requires defined conventions for PR titles and bodies, local CI validation for linting and formatting, and a pre-merge checklist to ensure code quality and consistent review handling before merging.

How do I run local CI validation before pushing code changes?

Local CI validation executes checks like linting and formatting on your current changes before pushing. This ensures code passes relevant local checks, maintaining consistent code quality and preventing pipeline failures.

What is the best way to manage code review comments efficiently?

Managing code review comments efficiently involves integrating with review-workflow tools to handle comments and verification systematically. This ensures all review feedback is addressed within the defined PR lifecycle.

Do I need specific Git workflow tools to use the pr-lifecycle Skill?

Using the pr-lifecycle Skill requires adherence to defined PR conventions and integrates with specific Git workflow tools like review-workflow and jj-safe-push to ensure consistent code quality and efficient review processes.

What should be included in a pre-merge checklist for a Pull Request?

A pre-merge checklist for a Pull Request should confirm that local CI validation passes, PR titles and bodies meet defined conventions, and all code review comments are addressed to ensure readiness for merging.

When do I need a standardized Pull Request workflow process?

A standardized Pull Request workflow process is needed in software development workflows requiring consistent code quality and efficient review processes, from feature implementation and local CI validation to final merging.