create-pr

Draft GitHub pull requests with detected issue closes and templates.

5|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/blamechris/chroxy --skill create-pr-blamechris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/blamechris/chroxy/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/blamechris/chroxy --skill create-pr-blamechris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the PR drafting process by detecting issues to close and applying consistent formatting guidelines, reducing manual PR writing time.

Core Features & Use Cases

  • Auto-detection of Issues to Close: scans commits, branch names, and from-review issues to generate Closes lines.
  • PR Draft Templates: default and batch-fix templates to maintain consistent PR bodies.
  • Guardrails and Validation: ensures PR targets main, validates branch state, and outlines steps to open the PR.

Quick Start

Provide a prepared PR draft using the detected closable issues and templates, then push a feature branch to create a PR against main.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automatically draft a GitHub pull request that closes linked issues?

To automatically draft a pull request that closes linked issues, this Skill scans commits, branch names, and from-review issues to construct a properly formatted PR body with accurate closes lines. It validates the branch state and generates the title and body.

Can I automatically generate a PR description for batch fixes against main?

Yes, you can generate a PR description for batch fixes against main. It applies specific batch-fix templates to maintain consistent PR bodies and enforces that the pull request targets the main branch before preparing the push commands.

How does issue detection work when generating pull request descriptions?

Issue detection for generating pull request descriptions works by scanning commit messages, parsing branch names, and identifying from-review issues. This determines which issues to close and automatically builds the corresponding closes lines in the PR draft.

What is the best way to ensure my PR targets main and validates branch state?

The best way to ensure your PR targets main and validates branch state is using built-in guardrails during the PR drafting process. It validates the current branch state, enforces the main target, and prepares the exact gh commands to push and open the PR.

Do I need the gh CLI to push a branch and open the PR using this automation?

Yes, you need the gh CLI to push a branch and open the PR using this automation. After detecting issues and applying templates, the Skill prepares the specific terminal commands required to push your feature branch and open the pull request via gh.

Are there limitations when drafting PRs for single versus batch fixes in GitHub workflows?

A limitation when drafting PRs for single versus batch fixes is that the Skill enforces targeting main and requires distinct templates. It differentiates between single and batch-fix templates to apply the correct formatting, and validates the branch state before generating commands.