create-pr

Name: create-pr
Availability: InStock
Author: Warp

Prepare pull requests with presubmit checks and Linear task links.

64.1k|5.4k|Updated Jul 8, 2021

Search Tags:#git #linting #code-review #pull-request #pr-workflow

Ready to run

npx skills add https://github.com/warpdotdev/warp --skill create-pr-warpdotdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/warpdotdev/warp/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/warpdotdev/warp --skill create-pr-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating pull requests efficiently with proper checks and documentation, reducing back-and-forth and merge delays.

Core Features & Use Cases

Presubmit-driven PRs: Enforces formatting, linting, tests, and required checks before opening PRs.
Link Linear tasks: Integrates with Linear tasks to ensure traceability from concept to code.
PR templates & guidelines: Provides standardized descriptions, branch naming, and review-ready changes for faster merging.

Quick Start

Open a feature branch and follow the specified PR workflow to prepare, review, and submit the pull request.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate pull request preparation and enforce presubmit checks?▼

Automating pull request preparation enforces formatting, linting, and required presubmit scripts before opening a PR. This ensures your feature branch passes all review-readiness checks and reduces back-and-forth delays during the merge process.

How do I link Linear tasks to a git pull request?▼

Linking Linear tasks to a pull request integrates task tracking directly with your code changes, ensuring traceability from concept to code. The PR workflow connects your feature branch to the corresponding Linear task during submission.

What is a review-ready pull request and when do I need it?▼

A review-ready pull request includes standardized documentation, branch naming conventions, and passing presubmit checks. You need it when merging feature branches to reduce merge delays and ensure proper code review standards.

Does this PR workflow require specific branch naming conventions and templates?▼

Yes, this PR workflow requires specific branch naming conventions, PR templating, and testing guidelines. These prerequisites ensure standardized descriptions and review-ready changes for faster merging.

What's the best way to streamline PR creation and reduce merge delays?▼

Streamlining PR creation involves applying presubmit-driven checks, Linear task linking, and PR templates. This standardized approach ensures proper documentation and review readiness, significantly reducing back-and-forth and merge delays.

Why does my pull request fail presubmit checks for linting and formatting?▼

Pull requests fail presubmit checks when formatting and linting standards are not met before submission. Enforcing these checks prior to opening a PR ensures code quality and prevents review bottlenecks.