raise-pull-requests

name	raise-pull-requests
description	Raise high-quality pull requests that are easy to review, provide clear context, and follow team conventions. Use when a user asks to open, write, prepare, or submit a pull request. Covers PR sizing, self-review, writing descriptions, submitting PRs, responding to review feedback, and reviewing others' PRs. Follows GitHub best practices for collaboration and code review.
license	MIT
compatibility	GitHub, GitHub CLI (gh) for PR commands
allowed-tools	Bash

Raise Pull Requests

Overview

A skill for raising pull requests that are easy to review, clearly described, and follow team conventions. Good pull requests reduce review time, catch bugs earlier, and keep the team informed about what is changing and why.

This skill covers the full lifecycle of a pull request — from preparing your changes through responding to review feedback.

Principles

1. Write Small, Focused Pull Requests

Each PR should fulfill a single purpose. Small PRs are easier and faster to review, leave less room for bugs, and provide a clearer history of changes. If your change touches multiple concerns, split it into separate PRs.

2. Provide Context and Guidance

Reviewers should not have to guess what your PR does or why. Write clear titles and descriptions, link related issues, and guide reviewers through the changes — especially when the PR touches multiple files.