skills.rest
onchainengineer
onchainengineerCOMMUNITY
Explore all skills by this author →
GitHub

pull-requests

Enforce pull request lifecycle, validation, and review workflows across repositories.

Updated Jan 28, 2026
Search Tags:#git#workflow#communication#branching#code-review#CI#pull-requests
One-click install
npx skills add https://github.com/onchainengineer/copilot-tree --skill pull-requests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-requests
Source: https://github.com/onchainengineer/copilot-tree/tree/main/.unix/skills/pull-requests
Command: npx skills add https://github.com/onchainengineer/copilot-tree --skill pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies the process for proposing and reviewing code changes to improve consistency and quality.

Core Features & Use Cases

  • Lifecycle Rules: Defines PR lifecycle, including squash merges, rebasing, and branch naming, to keep history clean.
  • Review & Validation: Specifies CI checks, code-review expectations, and PR body conventions to speed up approvals.
  • Collaboration Workflows: Guides cross-team communication and resolution of review feedback to maintain momentum.

Quick Start

  • Create a feature branch from main, open a PR with a descriptive title, and ensure all checks pass.
  • Follow the PR body structure and title conventions to communicate changes clearly.
  • Address review comments promptly and keep the PR up to date until it merges.

Frequently Asked Questions about pull-requests

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

FAQPage Schema
How do I create a pull request workflow that enforces code review and CI checks?▼

A pull request workflow enforcing code review and CI checks codifies PR body conventions, validation requirements, and review expectations to speed up approvals and maintain code quality consistently across teams.

What's the best way to manage branch naming and PR size for clean git history?▼

Managing branch naming and PR size for clean git history requires defining lifecycle rules for squash merges, rebasing, and naming conventions, which keeps repository history clean and improves development consistency.

How do I standardize pull request titles and body structures for cross-team communication?▼

Standardizing pull request titles and body structures for cross-team communication involves following defined PR body conventions and title rules to communicate changes clearly and maintain momentum when resolving review feedback.

Does this approach to pull requests work for teams needing strict validation checks before merging?▼

Yes, this pull request approach works for teams needing strict validation checks by specifying CI checks and code-review expectations that must pass before merging, ensuring safe and efficient collaboration across repositories.

When do I need to rebase or squash merge a pull request to keep repository history clean?▼

You need to rebase or squash merge a pull request to keep repository history clean when your lifecycle rules require it, ensuring merged changes maintain a clean main branch without fragmented or duplicate commits.

Related Skills

Explore More Software Engineering Skills→
zoeyzouzoeyzou

pr-workflow

A PRIME example of how to do it.

Community
Intermediate
marchattonmarchatton
5

landpr

Automate GitHub pull request merging with rebase or squash strategies.

Community
Advanced
ka2kamaka2kama
2

review-and-merge

Automate pull request review, feedback handling, and merge execution.

Community
Advanced
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

pr-description

Generate standardized pull request descriptions with structured templates and guidelines.

Official
Intermediate