pr

Name: pr
Availability: InStock
Author: amotion-ai

Create GitHub pull requests with summaries, test plans, and risk assessments.

Updated Apr 7, 2026

Search Tags:#automation #pull request #github #cli #linear #branch

Ready to run

npx skills add https://github.com/amotion-ai/botassist --skill pr-amotion-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/amotion-ai/botassist/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/amotion-ai/botassist --skill pr-amotion-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to compose comprehensive pull requests that include a clear summary, test plan, risk assessment, and a link to the associated ticket, leading to delays and miscommunication.

Core Features & Use Cases

Automated validation of branch state, uncommitted changes, and authentication before attempting a PR.
Dynamic PR content generation pulling commit messages, diff statistics, and optional Linear ticket details.
User confirmation step ensuring the PR title and body are reviewed and approved before creation.

Quick Start

Run /pr to generate and open a pull request for your current branch.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I create a GitHub pull request with a test plan and risk assessment from my feature branch?▼

Creating a GitHub pull request with a test plan and risk assessment requires running the skill on a feature branch with commits ahead of main, which dynamically generates PR content including a summary, test plan, and risk assessment for your confirmation before creation.

How do I link a Linear ticket to a GitHub pull request automatically?▼

Linking a Linear ticket to a GitHub pull request requires setting the optional LINEAR_API_KEY environment variable, which fetches ticket details and embeds the ticket link directly into the PR body alongside the generated summary.

Do I need the GitHub CLI installed to automate pull request creation?▼

Yes, the GitHub CLI installed and authenticated is required to automate pull request creation, as the skill relies on it to validate authentication, check uncommitted changes, and open the PR directly from your local feature branch.

What is the best way to ensure my pull request includes a clear summary of code changes before opening it?▼

The best way to ensure a pull request includes a clear summary is using an automated generator that pulls commit messages and diff statistics, providing a user confirmation step to review and approve the PR title and body before creation.

Why does automated pull request generation fail on an uncommitted branch?▼

Automated pull request generation fails on an uncommitted branch because the skill explicitly validates the branch state and uncommitted changes before attempting to create the PR, ensuring only committed code on feature branches ahead of main is summarized.