create-pr

Automate pull request creation and presubmit checks for Warp repository changes.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill create-pr-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/terzigolu/warp-lite/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/terzigolu/warp-lite --skill create-pr-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers efficiently create pull requests, ensure code quality through presubmit checks, and align changes with project workflows to speed up reviews and merges.

Core Features & Use Cases

  • Presubmit-verified PRs: ensures code is formatted, linted, and tested before submission.
  • Branching & naming guidance: enforces consistent branch names and PR titles.
  • Linking work items: ties PRs to Linear tasks for traceability.
  • PR templates & co-authoring: standardizes PR descriptions and attribution.

Quick Start

Open a feature branch and run the presubmit workflow to create and validate a 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 creation with presubmit checks?

Automating pull request creation involves running a presubmit workflow that enforces linting, formatting, and testing before submission. This ensures code quality and standardizes PR templates for faster reviews.

What is the best way to enforce branch naming and PR title conventions?

Enforcing branch naming and PR titles requires applying specific workflow guidelines during pull request creation. This standardizes naming conventions across feature branches, ensuring consistency and traceability throughout the project.

Can I standardize pull request descriptions and co-author attribution?

Standardizing pull request descriptions and co-author attribution uses predefined PR templates. This ensures consistent documentation of changes and proper credit assignment for collaborative coding efforts.

Why do I need presubmit checks before opening a pull request?

Presubmit checks are required before opening a pull request to verify code is formatted, linted, and tested. This pre-review workflow prevents build breaks and speeds up the merging process.

Does the pull request workflow support updating existing PRs?

The pull request workflow supports updating existing PRs by re-running the presubmit checks and modifying templates. This ensures ongoing changes maintain code quality and alignment throughout the review cycle.