skills.rest
rysweet
rysweetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Creating Pull Requests

Analyze commits and diffs to generate structured pull request descriptions.

2|22|Updated Oct 9, 2025
Search Tags:#template#documentation#PR#code-review#pull-request#tests
One-click install
npx skills add https://github.com/rysweet/azlin --skill creating-pull-requests-rysweet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Creating Pull Requests
Source: https://github.com/rysweet/azlin/tree/main/.claude/skills/collaboration/creating-pull-requests
Command: npx skills add https://github.com/rysweet/azlin --skill creating-pull-requests-rysweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates high-quality PRs with meaningful context, test plans, and reviewer-friendly descriptions to speed up reviews.

Core Features & Use Cases

  • Analyze commits and changes for PR context
  • Generate comprehensive PR descriptions and test plans
  • Enforce PR best practices and small, focused changes

Quick Start

Create a PR with a detailed description and test plan.

Frequently Asked Questions about Creating Pull Requests

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

FAQPage Schema
How do I write a pull request description that helps reviewers understand my changes?▼

A pull request description should include a concise summary, motivation for the changes, implementation details, test coverage, and any breaking changes. This context helps reviewers understand scope and intent quickly, accelerating code review.

What should I include in a PR template to follow best practices?▼

PR templates should enforce a structured format: title guidelines, changelog, motivation, implementation details, testing strategy, breaking changes, and rollout plan. Templates ensure consistency and provide reviewers with the information they need upfront.

How do I ensure my pull request is ready for review?▼

Run pre-flight checks including tests, linting, and builds before opening a PR. Verify commits are focused and changes are small. Include a comprehensive description with test plans so reviewers have complete context.

Can I analyze my commits to determine what my PR should cover?▼

Yes, analyzing commits and diffs reveals your change scope and intent. This analysis informs the PR description, helping you summarize what changed and why, making the PR more reviewer-friendly.

What's the best way to document testing in a pull request?▼

Include a detailed test plan in your PR description covering new functionality, edge cases, and regression testing. Document test results and any manual testing performed so reviewers can verify coverage.

Why should pull requests be small and focused?▼

Small, focused changes are easier to review, faster to merge, and reduce the risk of introducing bugs. They make code review efficient and help reviewers understand intent without context-switching across unrelated changes.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
1.2k

creating-pr

Create or update GitHub pull requests with conventional commits.

Official
Intermediate
mkalkeremkalkere
4

pr-complete

Verify GitHub PR readiness by checking approvals, CI status, mergeability, and notify humans via bus message.

Community
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
jota-batutajota-batuta

git-workflow-and-versioning

Standardize trunk-based development and atomic commits for CI/CD workflows.

Community
Intermediate