skills.rest
kubrickcode
kubrickcodeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prepare-pr

Generates bilingual PR titles and descriptions from git commit history.

1|Updated Mar 8, 2026
Search Tags:#git#code review#pull request#conventional commits#github#bilingual#pr description
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --skill prepare-pr-kubrickcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/kubrickcode/cine-mirror/tree/main/.agents/skills/prepare-pr
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill prepare-pr-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a clear pull request title and description for a branch with many commits is tedious and error-prone. This Skill analyzes all commits since divergence from the base branch and produces a consolidated, conventional-commit-style PR title and body in both Korean and English. ## Core Features & Use Cases - Commit Analysis: Runs git log and git diff against the auto-detected base branch to summarize commits and changed files. - Conventional Commit Titles: Selects the dominant commit type (feat, fix, refactor, etc.) by priority and generates a title under 50 characters. - Bilingual Output: Writes both Korean and English versions of the PR title and body to pr_content.md, including summary, changes, related issues, and test plan sections. - Use Case: After finishing a feature branch with eight mixed commits, run this Skill to get a ready-to-paste PR title and description, then create the PR with gh pr create. ## Quick Start Ask the assistant to prepare the PR content for the current branch against the main branch.

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 PR description from multiple commits?▼

Run this Skill on your feature branch and it analyzes all commits since divergence from the base branch using git log and git diff. It writes a consolidated PR title and body to pr_content.md in both Korean and English.

How is the PR title type chosen for mixed commits?▼

The Skill counts commit types and selects the dominant one using the priority order feat > fix > refactor > perf > docs > chore. For mixed feat and fix commits, feat takes precedence, and titles are kept under 50 characters.

Does this Skill create the actual pull request on GitHub?▼

No, it only generates PR content and writes it to pr_content.md. You can then use gh pr create with the generated file to open the pull request through the GitHub CLI.

What happens if the base branch cannot be detected?▼

The Skill tries origin/HEAD first, then falls back to origin/main and origin/master. You can also pass the base branch explicitly as an argument to bypass auto-detection.

When should I not use this PR generation approach?▼

For single-commit PRs, use the commit message directly instead of this Skill. It is designed for branches with multiple commits that need a consolidated description.

Related Skills

Explore More Software Engineering Skills→
duronextduronext
15

pr-create

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

Official
Advanced
cartridge-ggcartridge-gg
11

create-pr

Creates or updates a GitHub Pull Request from the current branch to main.

Official
Intermediate
LamseyahEliasLamseyahElias

requesting-code-review

Automate pre-commit security scans, quality gates, and auto-fixes for code diffs.

Community
Advanced
kevinrobaynakevinrobayna

update-pr

Update GitHub Pull Request titles and bodies via the GitHub CLI.

Community
Advanced