pr-creator

Create GitHub pull requests from specification documents using GitHub CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/B16B1RD/cc-craft-kit --skill pr-creator-b16b1rd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/B16B1RD/cc-craft-kit/tree/main/.claude/skills/pr-creator
Command: npx skills add https://github.com/B16B1RD/cc-craft-kit --skill pr-creator-b16b1rd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, textlint, markdownlint-cli2.

What problem does it solve?

Manually creating Pull Requests, especially with detailed descriptions and quality checks, is a repetitive and time-consuming task. This skill automates the entire PR creation process, ensuring consistent quality and freeing up developers to focus on coding.

Core Features & Use Cases

  • Automated PR Generation: Automatically creates GitHub Pull Requests when a specification moves to the 'completed' phase.
  • Quality Assurance: Integrates textlint for Japanese text proofreading and markdownlint for Markdown syntax validation, ensuring high-quality PR descriptions.
  • Structured PR Body: Generates a comprehensive PR body including summary, changes, test plan, and linked issues, based on the specification.
  • Use Case: After completing a feature, simply update its status to 'completed'. This skill will then automatically draft a well-structured Pull Request, complete with a detailed description and verified for linguistic and Markdown quality, ready for review.

Quick Start

Move the specification with ID 'feat-auth-001' to the 'completed' phase to automatically create a Pull Request. /cft:spec-phase feat-auth-001 completed

Frequently Asked Questions about pr-creator

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

FAQPage Schema
How do I automate creating GitHub pull requests from specification documents?

Automate GitHub pull request creation by transitioning a specification to the 'completed' phase. The Skill generates a PR title, composes a structured body with Overview, Changes, Test Plan, and Related Issue sections, then creates a draft PR via GitHub CLI while enforcing quality checks.

Can I validate Markdown and text quality in pull request descriptions?

Yes. The Skill integrates markdownlint to validate Markdown syntax and textlint for Japanese text proofreading, ensuring consistent quality standards in PR descriptions before submission.

What's the best way to ensure PR descriptions follow a consistent structure?

Use automated PR generation to enforce a standardized structure. The Skill creates PR bodies with predetermined sections—Overview, Changes, Test Plan, and Related Issue—eliminating manual formatting and reducing inconsistency across pull requests.

Does this work with GitHub and specification-based workflows?

Yes. The Skill integrates with GitHub CLI (gh) and activates when specifications transition to 'completed' status, making it ideal for workflows where implementation follows formal specification documents.

What happens if a PR description exceeds length limits?

The Skill enforces length limits on generated PR titles and descriptions to maintain readability and comply with GitHub best practices, truncating content as needed during draft creation.

Can I use this for CI/CD pipelines to auto-create PRs on completion?

Yes. The Skill automates PR creation triggered by specification phase transitions, integrating into CI/CD workflows to eliminate manual PR creation steps when features move to the completed phase.