create-pr

Create draft pull requests with linting and Linear issue context.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lutzcc1/claude-skills --skill create-pr-lutzcc1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/lutzcc1/claude-skills/tree/main/project/create-pr
Command: npx skills add https://github.com/lutzcc1/claude-skills --skill create-pr-lutzcc1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating high-quality pull requests by automating lint checks, diff reviews, and the generation of PR titles and descriptions that follow Sprout's conventions.

Core Features & Use Cases

  • Lint before PR to ensure code quality with rubocop and auto-fix where possible.
  • Analyze branch changes by reviewing commits and diffs to capture scope and impact.
  • Generate PR title and body using Linear issue context when available.
  • Create a draft PR and return the PR URL for easy sharing.

Quick Start

Trigger the skill when the user asks to create a PR; it will check the current branch, fetch Linear context if present, run linting, analyze commits, and draft the PR ready for review.

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 linting and Linear context?

You can automate pull request creation by running lint checks, analyzing branch diffs, and extracting Linear issue context to generate a standardized PR title and description automatically.

How does automated PR generation work with git and GitHub CLI?

Automated PR generation works by analyzing your current feature branch commits and diffs, running linters like rubocop, and using the GitHub CLI to create a draft PR with a convention-compliant title and body.

Can I use rubocop to auto-fix code before creating a GitHub pull request?

Yes, you can run rubocop to lint your code and apply auto-fixes before the PR generation process analyzes the changes and drafts the pull request for review.

Does automated PR drafting require Linear issue context to generate a title?

Automated PR drafting does not strictly require Linear issue context, but it fetches and uses this data when available to compose more accurate and standardized PR titles and descriptions.

What is the best way to enforce project conventions when creating a pull request?

The best way to enforce project conventions is to automate PR creation by running linters, validating branch changes, and generating a standardized title and description that adheres to your project's formatting rules.

What do I need to set up before automating draft PRs from my feature branch?

You need a current feature branch with commits, an accessible GitHub CLI environment, and optionally linked Linear issue context to successfully generate a draft PR URL and enforce conventions.