pr-create

Create pull requests with descriptions and test plans from branch commits using gh.

15|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/duronext/jig --skill pr-create-duronext
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/duronext/jig/tree/main/core/skills/pr-create
Command: npx skills add https://github.com/duronext/jig --skill pr-create-duronext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when creating a pull request. Analyzes branch changes, writes a clear PR description with friendly tone, and generates a structured test plan.

Core Features & Use Cases

  • Analyze commits across the feature branch and generate a concise PR body.
  • Detect ticket references from the branch or config and include them in the PR.
  • Generate a structured test plan outlining test cases and verification steps.
  • Push changes and create the PR using the configured git host.

Quick Start

Trigger the skill by saying create a PR, open a pull request, or typing /pr-create.

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 pull request description with a test plan?

To automatically generate a pull request, this skill analyzes your feature branch commits to create a concise PR body and a structured test plan. It reads jig.config.md for git host and ticket system settings, then uses gh to push and open the PR.

How do I ensure ticket references are included when creating a pull request?

To ensure ticket references are included in your pull request, the skill detects them automatically from your branch name or config. It reads ticket-prefix and require-ticket-reference from jig.config.md to assemble the PR metadata accurately.

Can I use gh to push changes and create a PR with a structured test plan?

Yes, you can use gh to push changes and create a PR with a structured test plan. The skill leverages the gh command-line tool to push your branch to the configured git host and assemble the PR with verification steps.

What is the best way to create a clear PR body from feature branch commits?

The best way to create a clear PR body is analyzing commits across the feature branch to generate a concise description with a friendly tone. This automation writes the PR body and outlines test cases during the ship stage.

Do I need a jig.config.md file to automate pull request creation?

Yes, you need a jig.config.md file to automate pull request creation. The skill reads this configuration for git-host, ticket-system, ticket-prefix, branching.format, require-ticket-reference, and main-branch to properly assemble PR metadata.

Why does my automated PR creation fail to detect the correct ticket system?

Automated PR creation may fail to detect the ticket system if jig.config.md lacks proper ticket-system or ticket-prefix values. Ensure your configuration explicitly defines these fields so the skill can correctly assemble and reference tickets in the PR.