pr-create

Generate GitHub pull request descriptions and test plans from branch diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CasaPerks/casaflow --skill pr-create-casaperks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/CasaPerks/casaflow/tree/main/core/skills/pr-create
Command: npx skills add https://github.com/CasaPerks/casaflow --skill pr-create-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the effort of writing a reviewer-friendly pull request by turning branch diffs and commit history into a structured PR description and a tailored test plan.

Core Features & Use Cases

  • Automated change review before PR creation: Runs a code review swarm and blocks PR creation when blocking/major issues are found.
  • Context-aware PR drafting: Detects ticket references from your branch naming and formats the PR body to match project conventions.
  • Structured test plan generation: Produces checkbox-based test steps based on the type of changes in the commits.
  • Feature flag change disclosure: Detects changes to feature-flags.* registry files, extracts JSDoc flag metadata, and inserts a required ## Flags section.
  • GitHub PR creation: Pushes the branch and opens a PR using gh pr create, including a properly formatted heredoc body.

Quick Start

Open your terminal, create or update your branch for the work, and run the skill by typing "/pr-create" to generate and submit a PR with a structured description, test plan, and any required flags section.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I automatically generate a GitHub pull request description from branch commits?

You can generate a GitHub pull request description by analyzing branch diffs and commit history to produce a structured PR body. This approach formats the description to match project conventions and includes a tailored test plan automatically.

How do I create a structured test plan for a pull request?

Creating a structured test plan for a pull request involves analyzing the types of changes in your commits. The process produces checkbox-based test steps directly within the PR body, ensuring reviewer-friendly validation criteria.

How does feature flag detection work when creating a PR from feature-flags files?

Feature flag detection works by identifying changes to `feature-flags.*` registry files during branch analysis. It extracts JSDoc flag metadata and inserts a required `## Flags` section into the PR description to disclose flag modifications.

Can I validate ticket references in my PR body using branch naming conventions?

Yes, you can validate ticket references by detecting them directly from your branch naming conventions. The PR drafting process formats the body to match project config conventions, ensuring ticket references are properly included.

Does the PR creation process block when a code review finds major issues?

Yes, the PR creation process runs a code review swarm first and blocks PR creation when blocking or major issues are found. This automated change review prevents problematic code from being submitted.

How do I push a branch and open a PR using the GitHub CLI with a formatted body?

Pushing a branch and opening a PR uses the `gh pr create` command with a properly formatted heredoc body. This submits the PR containing the structured description, test plan, and any required flags section.