pr

Automate structured pull request creation with titles, bodies, test plans, and linked issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of well-structured pull requests by ensuring a clear title, detailed description, test plan, and linked issues.

Core Features & Use Cases

  • Enforces title, body, and test plan structure for PRs.
  • Links related issues and references.
  • Guides the user through a review-ready PR workflow.

Quick Start

Prepare a review-ready PR for the current branch with a descriptive title, a concise body, and a complete test plan.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation for consistent code reviews?

Automating pull request creation applies a deterministic checklist to generate imperative titles, concise bodies, and test plans. This enforces a consistent structure across branch-based workflows, ensuring review-ready PRs with traceable issue references.

What is the best way to structure a GitHub pull request for quick reviews?

Structuring a GitHub pull request for quick reviews requires a clear title, detailed body, and linked issues. Applying a guided PR workflow ensures concise descriptions and complete test plans, producing consistent, review-ready documentation for code changes.

How do I link related issues and test plans when creating a PR?

Linking related issues and test plans when creating a PR is handled by enforcing specific body structure. The workflow guides you through adding traceable references and a complete test plan, ensuring all code changes connect to their originating issues.

Does this PR automation work with any branch-based workflow?

This PR automation works across branch-based workflows within GitHub projects. It applies deterministic guidance to ensure consistent titles, descriptions, and linked issues regardless of the specific branch strategy your team uses.

Why do my pull request titles and descriptions lack consistency across a team?

Pull request titles and descriptions lack consistency when teams do not follow a deterministic checklist. Applying an automated PR workflow enforces imperative titles and concise bodies, standardizing documentation and ensuring review-ready submissions.

What should a complete test plan include in a pull request?

A complete test plan in a pull request should include verification steps for code changes. The PR workflow enforces this structure, guiding you to document a concise test plan alongside a descriptive title and linked issues for traceable references.