create-pr

Automate PR creation from feature branches with rebasing, squashing, and Linear ticket linking.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Lightricks/ltx-analytics-agents --skill create-pr-lightricks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Lightricks/ltx-analytics-agents/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/Lightricks/ltx-analytics-agents --skill create-pr-lightricks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end PR workflow for Git-based projects, reducing manual overhead and human error by handling branch detection, base branch updating, commit consolidation, ticket linking, and PR creation with consistent messaging.

Core Features & Use Cases

  • Branch and base branch detection to determine the correct working context.
  • Rebase on the latest base branch with safeguards for uncommitted changes.
  • Smart commit handling: squash or preserve meaningful commits with context-aware messages.
  • Linear ticket detection and integration to attach context to PRs and updates.
  • Pushes and uploads PRs with structured metadata, including test plans and summaries.
  • Use Case: A feature branch CPDO-123 can be automatically prepared, linked to Linear, and opened as a PR with a coherent, reviewer-friendly description.

Quick Start

Create a PR for the current branch and link it to a Linear ticket if applicable.

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 from a Git feature branch?

Automating pull request creation involves detecting the feature branch, rebasing onto the latest base branch, squashing commits, and linking Linear tickets before pushing and opening the PR with structured metadata.

How does Linear ticket integration work when creating a PR?

Linear ticket integration works by parsing commit messages for ticket IDs and using the MCP API to fetch issue context, automatically attaching relevant Linear metadata to the PR description for reviewer clarity.

How do I handle uncommitted changes before rebasing a feature branch?

Handling uncommitted changes before rebasing requires applying safeguards to prevent data loss, ensuring the working directory is clean before the automated rebase onto the latest base branch occurs.

What is the best way to squash commits before opening a pull request?

The best way to squash commits is through context-aware handling that consolidates meaningful commits into coherent messages, ensuring the final PR history is reviewer-friendly and logically structured.

Can I use this automated PR workflow without configuring Linear integration?

You can use this workflow without Linear if no ticket IDs are found in commits, but the full value comes from automatically linking issues and attaching context to the PR via the MCP API.

Does automated branch management detect the correct base branch for my PR?

Automated branch management detects the correct base branch by analyzing the repository structure and working context, ensuring the pull request targets the appropriate integration branch before rebasing.