git-pr

Generate Korean-context Git PR titles and bodies for AX-WMS projects.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill git-pr-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/git-pr
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill git-pr-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and inconsistency of writing Git PR titles and bodies that align with the AX-WMS project's specific formatting rules, Korean language context, monorepo scope guidelines, and GitFlow workflow, ensuring all PRs are clear, searchable, and easy for reviewers to process.

Core Features & Use Cases

  • Compliant PR Title Generation: Automatically creates PR titles that follow the project's [Type(scope)]: subject format, adhere to Korean phrasing rules (noun endings, no action verbs, under 50 characters), and use the correct monorepo scope (web, api, ai, infra, docs, agent).
  • Standardized PR Body Creation: Builds PR bodies using the project's required template with pre-structured sections for Type of change checklists, Motivation, Problem Solving, and reviewer notes.
  • Use Case: When you complete a bug fix for the AX-WMS API, use this Skill to generate a ready-to-use, rule-compliant PR title and body in seconds, no need to manually reference formatting guidelines.

Quick Start

Use the git-pr skill to generate a properly formatted PR title and body for your recent AX-WMS API bug fix.

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I format a Korean pull request title for a monorepo project?

To format a Korean pull request title for a monorepo, use the [Type(scope)]: subject structure. The scope must match your monorepo directory like api or web, and the subject should use Korean noun endings under 50 characters.

What should be included in a Git PR body for AX-WMS bug fixes?

A Git PR body for AX-WMS bug fixes should include a Type of change checklist, Motivation, Problem Solving, and reviewer notes sections. This standardized template ensures clear communication and easy processing for project reviewers.

How do I create a compliant Git PR for AX-WMS following GitFlow?

To create a compliant Git PR for AX-WMS following GitFlow, generate a title with the correct [Type(scope)]: subject format and a body using the project template. This supports routine development, hotfix, and documentation workflows.

What are the monorepo scope guidelines for AX-WMS pull requests?

The monorepo scope guidelines for AX-WMS pull requests require selecting the correct scope from web, api, ai, infra, docs, or agent. This scope is inserted into the [Type(scope)]: subject title format to categorize the changes accurately.

Does the AX-WMS PR template support hotfix and documentation workflows?

Yes, the AX-WMS PR template supports hotfix and documentation workflows alongside routine development and bug fixes. It generates appropriately typed PR titles and standardized bodies aligning with the lightweight GitFlow strategy.

Why do Korean PR titles need noun endings instead of action verbs?

Korean PR titles need noun endings instead of action verbs to adhere to project phrasing standards and maintain consistency. This formatting rule ensures all pull request subjects remain concise, searchable, and under 50 characters.