create-pr

Create GitHub pull requests with issue-linked descriptions and reviewer assignments.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill create-pr-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/tomzx/agents/tree/main/skills/create-pr
Command: npx skills add https://github.com/tomzx/agents --skill create-pr-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating pull requests often involves manually composing descriptions that map code changes to an issue, link reviewers, and ensure acceptance criteria. This skill automates that process, reducing time and ensuring consistency across PRs.

Core Features & Use Cases

  • Generate a PR title and body that map implementation changes to acceptance criteria and link to the related issue.
  • Assign reviewers and manage draft vs. ready-for-review states based on coverage.
  • Validate prerequisites (branch ahead of the base, tests passing) before PR creation.
  • Use in teams following issue-driven development to standardize PRs and streamline code reviews.

Quick Start

Provide the repository and optional issue number to create a structured PR description for the current branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with structured descriptions?

Automating GitHub pull request creation involves generating a structured, issue-linked description that maps implementation changes to acceptance criteria. This skill validates prerequisites like branch state and passing tests before creating the PR.

Can I automatically assign reviewers and manage draft states when creating a pull request?

Yes, you can assign reviewers and manage draft versus ready-for-review states based on code coverage. The skill evaluates coverage metrics to determine whether the pull request should be opened as a draft or marked ready for review.

What prerequisites are required before creating an issue-linked pull request?

Creating an issue-linked pull request requires your branch to be ahead of the base branch and all tests to be passing. The skill enforces these prerequisites before generating the PR title and body.

How do I map code changes to acceptance criteria in a pull request description?

Mapping code changes to acceptance criteria is done by generating a PR body that explicitly links implementation details to the related issue. This standardizes PRs for teams following issue-driven development workflows.

What is the best way to standardize pull requests for issue-driven development?

Standardizing pull requests for issue-driven development is achieved by automating the generation of structured descriptions that link reviewers and acceptance criteria. This ensures consistency across PRs and streamlines the code review process.

Why does pull request creation fail if my branch is not ahead of the base branch?

Pull request creation fails because the skill enforces an ahead-of-branch state prerequisite to ensure there are valid changes to merge. This validation prevents empty pull requests and guarantees the branch has implementation changes to map.