skills.rest
Cygnusfear
CygnusfearCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-pr

Create pull requests with linked issues and closing keywords.

5|3|Updated Oct 23, 2025
Search Tags:#git#code review#documentation#collaboration#pull request#workflow automation#commit message
One-click install
npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/create-pr
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating high-quality pull requests with clear commit messages and detailed descriptions is crucial for effective collaboration but can be time-consuming and inconsistent. This skill guides the creation of PRs following best practices, ensuring clarity, consistency, and impact.

Core Features & Use Cases

  • Clear & Concise Writing: Integrates with the writing-clearly-and-concisely skill to ensure all PR prose is professional and easy to understand.
  • Conventional Commit Messages: Guides the creation of commit messages with conventional types and imaginative emoji narratives, making history engaging and informative.
  • Structured PR Descriptions: Provides a template for comprehensive PR descriptions covering key changes, testing notes, related issues, and architectural impact.
  • Use Case: After completing a feature, use this skill to automatically generate a well-structured pull request, complete with a creative commit message and a comprehensive description, ready for efficient review and merge.

Quick Start

Use the writing-clearly-and-concisely skill to ensure clear, concise writing.

Then, follow the pr_guide.md for structure.

Example Commit Message (from guide)

feat: 🐋🎣 Implement large balance support

Example PR Description (from guide)

TITLE: feat: 🧙⛓️ Implement dynamic chain support from blockchain provider registry

Brief description of what changed and why it was needed.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation with issue linking and auto-close keywords?▼

Pull request automation ensures related issues are linked and closing keywords like Closes or Fixes are included in the PR body. This skill automates that process by identifying related issues, collecting context, and composing PR descriptions with change summaries and testing notes, streamlining code review workflows across GitHub branches and repositories.

What should a pull request description include for effective code review?▼

Effective PR descriptions cover key changes made, testing notes validating the work, related issue references, and architectural impact. This skill provides a structured template that guides you through composing comprehensive descriptions, ensuring clarity and consistency so reviewers understand the change's scope and implications without extra back-and-forth.

How do I write conventional commit messages that improve repository history?▼

Conventional commit messages use structured types and creative formatting to make git history engaging and searchable. This skill guides message creation with conventional types and emoji narratives, helping teams maintain informative commit logs that document intent and changes clearly for future maintainers.

Can I use this for pull requests across multiple repositories and branches?▼

Yes, this skill applies to GitHub workflows across branches and repositories. It automates PR creation whenever you need to ensure issues are associated and auto-closed on merge, making it suitable for multi-repo collaboration patterns where consistent linking and closing conventions are required.

Why is linking issues to pull requests important in collaboration?▼

Linking issues to pull requests creates traceability, enables automatic issue closure on merge, and provides reviewers with full context about what problem the code solves. This skill ensures that linkage happens consistently by automating the collection of related issues and insertion of closing keywords in every PR.

What's the best way to maintain clear, concise writing in pull request documentation?▼

Pull request documentation should be professional and easy to understand. This skill integrates with writing-clearly-and-concisely practices to ensure all PR prose is polished, then applies a structured template for descriptions so your communication is both thorough and accessible to reviewers.

Related Skills

Explore More Software Engineering Skills→
mkaczkowskimkaczkowski
3

Commit Message Generator

Generate conventional commit messages from git diff changes.

Community
Intermediate
smallnestsmallnest
207

ship-it

Commit changes, create and merge a pull request, and close the linked GitHub issue.

Community
Advanced
UntLabUntLab
1

git-workflow

Automate Git and GitHub workflows with Conventional Commits and branch strategies.

Community
Intermediate
Leep-GHLeep-GH

pr-lifecycle

Automate GitHub issue-to-PR-to-merge workflows with readiness checks.

Community
Advanced