commit-pr-hd

Automate commit, branch creation, and pull request workflows on repositories.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill commit-pr-hd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-pr-hd
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/hyeondongs-harness/skills/commit-pr-hd
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill commit-pr-hd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 커밋에서 PR 오픈까지의 전체 워크플로우를 자동화하여 수동 작업을 줄이고 PR 사이클을 단축합니다.

Core Features & Use Cases

  • 자동 브랜치 생성 및 네이밍 규칙 준수
  • 커밋 및 PR 오픈까지의 엔드-투-엔드 워크플로우 실행
  • diff 분석 기반 브랜치 네이밍 제안 및 다수 시나리오 지원

Quick Start

브랜치가 자동으로 생성되고 PR이 열리도록 워크플로우를 실행합니다.

Frequently Asked Questions about commit-pr-hd

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

FAQPage Schema
How do I automate git commit and pull request workflow end to end?

You can automate the git commit and pull request workflow end to end by running a single command that handles branch creation, commit, and PR opening, reducing manual work and shortening the PR cycle.

Can I enforce deterministic branch naming for feature development and hotfix cycles?

Yes, deterministic branch naming is enforced automatically for feature development and hotfix cycles across multiple git branching scenarios, ensuring consistent branch names and audit-friendly history without manual intervention.

How does diff analysis work for branch naming proposals?

Diff analysis evaluates code changes to propose relevant branch names, supporting multiple git branching scenarios to ensure deterministic naming and audit-friendly history.

What's the best way to shorten the PR cycle for code review automation?

The best way to shorten the PR cycle is to run an end-to-end workflow that automates branch creation, commit, and PR opening steps, minimizing manual work and accelerating code review automation.

Does this git workflow automation require any additional dependencies or components?

No additional dependencies or components are required to run the git workflow automation, allowing you to execute the end-to-end commit and PR workflow directly without extra setup.

Why use automated branch creation instead of manual git workflow steps?

Automated branch creation eliminates manual work, enforces deterministic naming rules, and generates audit-friendly history, ensuring consistency across feature development and hotfix cycles.