commit-pr

Automates git commit, branch creation, and pull request initiation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end workflow of making a commit, creating a feature branch, and opening a pull request, reducing manual steps and ensuring consistency across repositories.

Core Features & Use Cases

  • End-to-end Git workflow automation: commit, branch creation, and PR initiation with optional draft PR generation.
  • Enforces project override rules and branch naming conventions to maintain consistency.
  • Supports project-wide workflow automation for Be-Harness style repositories and standard PR practices.

Quick Start

Create or update a feature branch following the naming convention and open a draft PR.

Frequently Asked Questions about commit-pr

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

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

Automating a git commit to pull request workflow involves creating a feature branch, committing changes, and opening a PR. This process ensures standardized branch naming and consistent PR initialization across repositories.

Can I generate a draft pull request automatically after making a commit?

Yes, you can generate a draft pull request automatically after a commit. End-to-end git workflow automation supports optional draft PR generation alongside branch creation to streamline repository collaboration safely.

How do I enforce branch naming conventions for new pull requests?

To enforce branch naming conventions for pull requests, you apply project-specific override handling during branch creation. This maintains consistency across repositories by validating branch names before PR initialization.

Does this git workflow automation support project-specific override rules?

Yes, this git workflow automation supports project-specific override rules. It enforces project override rules and branch naming conventions to maintain consistency, particularly for Be-Harness style repositories and standard PR practices.

What is the best way to standardize pull request creation across multiple repositories?

The best way to standardize pull request creation is using end-to-end git workflow automation. It enforces branch naming conventions and project override rules, ensuring safe operation with validation across all repository collaboration scenarios.