git-ops

Generate Korean commit messages and create PRs via gh pr create.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/HuveD/agent-skillset --skill git-ops-huved
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/HuveD/agent-skillset/tree/main/git-ops
Command: npx skills add https://github.com/HuveD/agent-skillset --skill git-ops-huved

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

Git ์ปค๋ฐ‹ ์ž‘์„ฑ๊ณผ ๋กœ์ปฌ ์ปค๋ฐ‹ ์‹คํ–‰, PR ์ƒ์„ฑ(gh pr create) ์›Œํฌํ”Œ๋กœ์šฐ๋ฅผ ํ‘œ์ค€ํ™”ํ•˜์—ฌ ํŒ€ ํ˜‘์—…์˜ ์ผ๊ด€์„ฑ๊ณผ ์†๋„๋ฅผ ๋†’์ธ๋‹ค.

Core Features & Use Cases

  • ์ปค๋ฐ‹ ์š”์ฒญ ์‹œ๋‚˜๋ฆฌ์˜ค์— ๋”ฐ๋ผ ๋ณ€๊ฒฝ์„ ๋ถ„์„ํ•˜๊ณ  ํ•œ๊ธ€ ์ปค๋ฐ‹ ๋ฉ”์‹œ์ง€๋ฅผ ์ž๋™์œผ๋กœ ์ƒ์„ฑํ•œ๋‹ค.
  • PR ์ƒ์„ฑ ์‹œ ๊ธฐ๋ณธ ๋ธŒ๋žœ์น˜๋ฅผ ๊ธฐ์ค€์œผ๋กœ ์ œ๋ชฉ/๋ณธ๋ฌธ์„ ์ƒ์„ฑํ•˜๊ณ  gh pr create ๋ช…๋ น์„ ํ†ตํ•ด PR์„ ๋งŒ๋“ ๋‹ค.
  • Git ๋ณ€๊ฒฝ ์š”์•ฝ ๋ฐ ๋ฉ”์‹œ์ง€ ์ž‘์„ฑ ๊ทœ์น™์„ ์ผ๊ด€๋˜๊ฒŒ ์ ์šฉํ•˜์—ฌ ํ˜‘์—… ํ’ˆ์งˆ์„ ๋†’์ธ๋‹ค.

Quick Start

์ €์žฅ์†Œ์˜ ๋ณ€๊ฒฝ ๋‚ด์šฉ์„ ๊ฐ€์žฅ ์ตœ๊ทผ ์ปค๋ฐ‹ ๊ทœ์น™์œผ๋กœ ์ปค๋ฐ‹ํ•˜๊ณ  ๊ธฐ๋ณธ ๋ธŒ๋žœ์น˜๋กœ PR์„ ์ƒ์„ฑํ•˜๋Š” ์›Œํฌํ”Œ๋กœ์šฐ๋ฅผ ์ฆ‰์‹œ ์‹œ์ž‘ํ•œ๋‹ค.

Frequently Asked Questions about git-ops

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

FAQPage Schema
How do I automate git commit message generation for feature branches?โ–ผ

Automating git commit message generation standardizes your workflow by analyzing repository changes and producing Korean commit messages aligned with project conventions. It stages all local changes deterministically before committing to a feature branch.

What is the best way to automate GitHub pull request creation from the command line?โ–ผ

Automating GitHub pull request creation uses gh pr create to generate the PR title and body against the base branch. This standardizes the PR workflow, ensuring consistent documentation of feature branch changes for team collaboration.

Can I standardize DevOps git workflows to enforce consistent commit conventions?โ–ผ

Standardizing DevOps git workflows enforces consistent commit conventions by applying uniform rules for Git change summaries and message writing. This improves collaboration quality and speeds up the development process across feature branches.

Does the automated git workflow support generating PR titles and bodies against a base branch?โ–ผ

The automated git workflow supports generating PR titles and bodies by comparing feature branch changes against the base branch. It then executes gh pr create to automatically submit the pull request with standardized documentation.

Why does the git workflow stage all local changes before generating a commit?โ–ผ

The git workflow stages all local changes before generating a commit to ensure deterministic local commits. By staging everything deterministically, it accurately analyzes the full scope of changes to produce compliant commit messages.