git-pr

Generate PR titles and descriptions following [Type(scope)]: Subject format.

Updated Jun 5, 2026
Ready to run
npx skills add https://github.com/KangJiSseok/ACODIAN --skill git-pr-kangjisseok
๐Ÿ’ฌ Prompt for ChatGPT / Claude Chatโ–ผ
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/git-pr
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill git-pr-kangjisseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ํ˜„์žฌ AX-WMS ํ”„๋กœ์ ํŠธ์˜ PR ์ œ๋ชฉ๊ณผ ๋ณธ๋ฌธ์„ ํ•œ๊ธ€ ๋งฅ๋ฝ์— ๋งž๊ฒŒ ์ž‘์„ฑํ•˜๋„๋ก ๋•์Šต๋‹ˆ๋‹ค. ์‚ฌ์šฉ์ž๊ฐ€ PR ์ œ๋ชฉ/๋ณธ๋ฌธ์„ ๋งŒ๋“ค์–ด๋‹ฌ๋ผ๊ณ  ํ•˜๊ฑฐ๋‚˜, ๋ฆฌ๋ทฐ์–ด๊ฐ€ ์ดํ•ดํ•˜๊ธฐ ์‰ฌ์šด PR ์„ค๋ช…์„ ์ •๋ฆฌํ•ด๋‹ฌ๋ผ๊ณ  ํ•  ๋•Œ ์‚ฌ์šฉํ•ฉ๋‹ˆ๋‹ค.

Core Features & Use Cases

  • PR ์ œ๋ชฉ ํ˜•์‹๊ณผ ์„ค๋ช…์˜ ๊ฐ„๊ฒฐ์„ฑ ๊ฐ€์ด๋“œ ์ œ๊ณต
  • GitFlow ๊ฒฝ๋Ÿ‰ ์ „๋žต ๋ฐ ๋ชจ๋…ธ๋ ˆํฌ ๊ตฌ์กฐ์— ๋งž์ถ˜ ์ผ๊ด€๋œ PR ๊ทœ์น™ ์ œ์‹œ
  • ํ•œ๊ธ€ ๋งฅ๋ฝ์—์„œ ์ดํ•ดํ•˜๊ธฐ ์‰ฌ์šด PR ์„ค๋ช…์œผ๋กœ ๋ฆฌ๋ทฐ ์†๋„ ํ–ฅ์ƒ
  • ๋ณ€๊ฒฝ ๋ฒ”์œ„ ์š”์•ฝ ๋ฐ ์ค‘์š”ํ•œ ํฌ์ธํŠธ๋ฅผ ์ž๋™์œผ๋กœ ๊ฐ•์กฐํ•˜๋Š” ๋ณด์กฐ ๊ธฐ๋Šฅ

Quick Start

AX-WMS ํ”„๋กœ์ ํŠธ์˜ PR ์ œ๋ชฉ๊ณผ ๋ณธ๋ฌธ ์ž‘์„ฑ์„ ์š”์ฒญํ•˜๋ฉด ์ฆ‰์‹œ ์ดˆ์•ˆ์„ ์ œ๊ณตํ•ฉ๋‹ˆ๋‹ค.

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I write a pull request title for a monorepo with multiple scopes?โ–ผ

To write a pull request title for a monorepo, use a standardized format like [Type(scope)]: Subject. Scopes help categorize changes across web, api, ai, infra, docs, or agent directories to clarify the modification area.

What is the best way to generate a code review description that follows GitFlow conventions?โ–ผ

Generating a code review description that follows GitFlow conventions involves summarizing the change scope and highlighting key points concisely. This ensures reviewers understand the lightweight GitFlow strategy and branch context quickly.

Can I automate PR formatting for specific project contexts like AX-WMS?โ–ผ

Yes, you can automate PR formatting for specific contexts like AX-WMS by enforcing repository-specific review guidelines. This ensures titles and descriptions match the required Korean context and project standards automatically.

How do I create a concise PR summary for reviewers in a Korean development context?โ–ผ

Creating a concise PR summary for reviewers in a Korean context requires emphasizing important changes and outlining the modification scope clearly. This approach reduces review time by providing straightforward Korean explanations.

Does GitFlow lightweight strategy support optional scopes like infra and agent?โ–ผ

Yes, the lightweight GitFlow strategy supports optional scopes including infra and agent. This allows monorepo structures to categorize pull requests effectively across diverse operational layers without rigid branching restrictions.

Why does my pull request title format keep failing code review checks?โ–ผ

Your pull request title format may fail code review checks if it lacks the required [Type(scope)]: Subject structure. Enforcing naming conventions ensures compliance with review guidelines and maintains monorepo consistency.