gen-pr

Generate Markdown PR descriptions from GitHub branch names and issues.

16|3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Yomiamy/flutter_inspector_kit --skill gen-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-pr
Source: https://github.com/Yomiamy/flutter_inspector_kit/tree/main/.claude/skills/gen-pr
Command: npx skills add https://github.com/Yomiamy/flutter_inspector_kit --skill gen-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, github-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of writing, editing, shortening, and standardizing PR descriptions for changes merging into a specified branch, such as origin/main. It integrates with GitHub issues for context and produces ready-to-use Markdown PR descriptions in zh-tw with retained en-us technical terms.

Core Features & Use Cases

  • PR Description Drafting: Automatically generates PR description drafts based on GitHub branch names and issues.
  • Issue Integration: Pulls issue details and context directly into the PR description.
  • Markdown Format: Outputs PR descriptions in zh-tw with en-us technical terms for clarity.
  • Use Case: When a developer needs to create a PR for a BUG-1691 issue, using this Skill can automatically pull the issue details, create a PR description, and prepare for review.

Quick Start

Use the gen-pr skill with the branch name for the change you wish to merge, such as gen-pr fix/202604/BUG-1691-product-gift-layout-issue.

Frequently Asked Questions about gen-pr

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

FAQPage Schema
How do I automatically generate a PR description from a GitHub branch name and issue?

To generate a PR description, you provide the GitHub branch name to the tool, which then resolves the linked issue details via GitHub MCP tools or local scripts to produce a ready-to-use Markdown draft.

Can I integrate GitHub issue context directly into my Markdown PR description?

Yes, you can integrate GitHub issue context directly into your Markdown PR description by using the tool's issue resolution feature to pull issue details and prepare the draft for code review.

Do I need GitHub CLI and MCP tools to automate PR description generation?

Yes, you need GitHub access with dependencies including `git`, `gh`, and `github-mcp` to resolve issue details and automate PR description generation from your branches.

What is the best way to draft a standardized PR description for a specific bug fix branch?

The best way to draft a standardized PR description for a bug fix branch is to use an automated generation skill that reads the branch name, pulls the linked issue, and outputs a standardized Markdown template.

Does the generated PR description support custom PR templates and checklist items?

Yes, the generated PR description supports custom PR templates and checklist items, outputting the final Markdown draft with retained English technical terms for clarity.

Why are my PR descriptions not pulling the correct issue details from my branch name?

PR descriptions fail to pull correct issue details when GitHub access is misconfigured or the branch name lacks the issue identifier required by the local scripts or GitHub MCP tools to resolve context.