skills.rest
specvital
specvitalOFFICIAL
Explore all skills by this author →
GitHub

prepare-pr

Generate bilingual Korean and English PR titles and descriptions from commits.

1|Updated Dec 8, 2025
Search Tags:#automation#Git#PR#generate#bilingual#conventional-commits
One-click install
npx skills add https://github.com/specvital/infra --skill prepare-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/specvital/infra/tree/main/.claude/skills/prepare-pr
Command: npx skills add https://github.com/specvital/infra --skill prepare-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a concise PR title and a detailed, bilingual (Korean and English) description from a collection of commits, ensuring consistency when consolidating work into a single PR.

Core Features & Use Cases

  • Consolidated PR Content: Generates a single Conventional Commits style title and a well-structured description.
  • Base Branch Detection & Commit Analysis: Detects the base branch automatically, collects commits since divergence, and analyzes changed files.
  • PR Content Output & Quick Copy: Saves the output to pr_content.md with both Korean and English versions for easy copying into GitHub PR forms.
  • Use Case: When you have multiple commits across a feature branch that need to be explained succinctly in one PR.

Quick Start

Run the prepare-pr skill on a multi-commit feature branch to generate bilingual PR content and save it to pr_content.md.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I generate a pull request description from multiple commits?▼

To generate a pull request description from multiple commits, automation tools consolidate commit histories and changed files into a single, structured PR briefing with a Conventional Commits title and summary.

What is the best way to write a bilingual PR title and body for GitHub?▼

The best way to write a bilingual PR title and body is to use an automation tool that outputs both Korean and English versions side-by-side in a markdown file, allowing direct copying into GitHub PR forms.

Does automated PR generation follow Conventional Commits formatting?▼

Yes, automated PR generation can follow Conventional Commits formatting by analyzing your commit history and deriving a standardized PR title that reflects the nature and scope of the combined changes.

Can I automatically detect the base branch and collect commits for a PR?▼

Yes, you can automatically detect the base branch and collect commits by running a PR preparation script that identifies branch divergence and analyzes all subsequent commit changes for the PR briefing.

How do I include a test plan and related issues in an automated PR description?▼

To include a test plan and related issues in an automated PR description, the generation process structures the output markdown with dedicated sections for summary, changes, related issues, and an optional test plan.

What file format is used to save consolidated PR content for easy copying?▼

Consolidated PR content is typically saved to a markdown file, such as pr_content.md, which stores the bilingual titles and descriptions for quick access and manual pasting into the pull request interface.

Related Skills

Explore More Software Engineering Skills→
ivklgnivklgn
11

load-branch-changes

Load current branch diffs, commits, and changed files into session context.

Community
Intermediate
flosrnflosrn

create-pr

Create and push pull requests with auto-generated titles and descriptions.

Community
Intermediate
timhiebenthaltimhiebenthal
17

commit-message-creator

Lint git commit messages against the Conventional Commits specification.

Community
Intermediate
kevinrobaynakevinrobayna

create-pr

Create draft GitHub pull requests with conventional commit titles.

Community
Intermediate