git-pr

Enforce Conventional Commits and automate PR workflows on git events.

Updated May 5, 2026
One-click install
npx skills add https://github.com/sonhaicoder/haiclaudeskill --skill git-pr-sonhaicoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/sonhaicoder/haiclaudeskill/tree/main/skills/git-pr
Command: npx skills add https://github.com/sonhaicoder/haiclaudeskill --skill git-pr-sonhaicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a consistent git-driven workflow by auto-triggering actions on common events such as commits, pushes, PR creations, reviews, branch operations, and changelog maintenance, reducing manual overhead and miscommunication.

Core Features & Use Cases

  • Auto-triggers on: git commit, git push, PR creation, pull request reviews, branch operations, and changelog references.
  • Provides a standardized approach for Conventional Commits formatting and PR documentation to streamline reviews and releases.
  • Applies to typical software-engineering workflows including feature development, bug fixes, and maintenance tasks.

Quick Start

Follow the defined triggers to auto-run PR workflows and enforce commit conventions.

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I enforce conventional commits in a collaborative git workflow?

To enforce conventional commits in a git workflow, you need standardized triggers for commits and PR creation. This approach automates commit messaging rules and PR documentation to streamline reviews and reduce manual overhead.

How do I automate pull request creation and branch management?

Automating pull request creation and branch management involves defining triggers for pushes, PR reviews, and branch operations. This standardizes PR documentation and ensures consistent workflows across feature development and bug fixes.

What is a conventional commits workflow and when do I need it?

A conventional commits workflow applies standardized formatting to commit messages and PRs to streamline reviews and releases. You need it for collaborative software engineering to reduce miscommunication and maintain changelog references.

Can I auto-trigger actions for changelog maintenance on git push?

Yes, you can auto-trigger actions for changelog maintenance on git push. Defining triggers for pushes and commits ensures changelog references are updated automatically, reducing manual overhead in software teams.

What's the best way to coordinate branches and PRs for code review?

The best way to coordinate branches and PRs for code review is applying automated rules for PR-ready workflows. This enforces consistent commit messaging and PR documentation, streamlining reviews and releases for collaborative teams.