skills.rest
remix-run
remix-runOFFICIAL
Explore all skills by this author →
Website𝕏@remix_runGitHub

make-pr

Draft and open GitHub pull requests with concise descriptions via gh CLI.

33.3k|2.8k|Updated Oct 26, 2020
Search Tags:#workflow#documentation#github#pr#code-review#pull-request
One-click install
npx skills add https://github.com/remix-run/remix --skill make-pr-remix-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-pr
Source: https://github.com/remix-run/remix/tree/main/.agents/skills/make-pr
Command: npx skills add https://github.com/remix-run/remix --skill make-pr-remix-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft and open GitHub pull requests with clear, reviewer-friendly descriptions that emphasize context and usage examples.

Core Features & Use Cases

  • Draft PR bodies that focus on change rationale, context links, and practical code examples.
  • Ensure PRs follow a consistent, minimal structure without unnecessary validation or testing sections.
  • Use when asked to open or prepare a PR to accelerate code reviews and merge readiness.

Quick Start

Draft a PR with a concise body and open it using the gh pr create command.

Frequently Asked Questions about make-pr

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

FAQPage Schema
How do I draft a GitHub pull request description for faster code review?▼

Drafting a GitHub pull request for faster review requires a concise body emphasizing change rationale, context links, and practical code examples. This ensures reviewer-friendly descriptions by focusing on high-signal content and avoiding boilerplate sections.

What should be included in a GitHub PR body to improve merge readiness?▼

A GitHub PR body should include clear context, related links, and usage code examples to improve merge readiness. Maintaining a minimal PR structure without boilerplate validation sections helps reviewers understand the changes quickly and accelerates the merge process.

Can I use the gh CLI to open a pull request from a prepared branch?▼

Yes, you can use the gh CLI to open a pull request from a prepared branch. The workflow utilizes the gh pr create command to generate the PR on GitHub after drafting a concise, reviewer-friendly description focused on context and code examples.

Does an effective pull request template need validation and testing sections?▼

An effective pull request does not need boilerplate validation or testing sections. To ensure a minimal PR structure, the description should omit these sections and instead focus entirely on change rationale, context links, and practical usage examples for the reviewer.

What is the best way to structure a pull request for a code review?▼

The best way to structure a pull request for code review is to maintain a minimal format that emphasizes the change rationale and provides practical code examples. This approach avoids unnecessary boilerplate and uses concise context to accelerate the review process.

Why should I exclude boilerplate sections from my GitHub pull request descriptions?▼

You should exclude boilerplate sections from GitHub pull request descriptions to enforce a minimal PR structure. Removing generic validation and testing sections ensures the PR body remains high-signal, allowing reviewers to focus strictly on the specific code changes and rationale.

Related Skills

Explore More Software Engineering Skills→
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
TencentTencent
19.5k

引用生成器

Generate standardized citations in APA, MLA, Chicago, and simplified formats.

Official
Basic
cbleckercblecker
5

creating-pull-request

Automate GitHub pull request creation with branch pushing and PR metadata.

Community
Basic
techwithanirudhtechwithanirudh
167

create-changeset

Analyze git commit history and generate changeset markdown files.

Community
Intermediate