pr-commiter

Enforce branch and PR policies during Git commits with explicit path selection.

131|13|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/regenrek/agent-skills --skill pr-commiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-commiter
Source: https://github.com/regenrek/agent-skills/tree/main/skills/pr-commiter
Command: npx skills add https://github.com/regenrek/agent-skills --skill pr-commiter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

Prevents chaotic commits and manual PR handling by providing a deterministic PR committer that enforces branch workflows and explicit path changes only.

Core Features & Use Cases

  • Deterministic commits with explicit path selection, ensuring safe and auditable changes.
  • Branch management and automated PR creation with policy checks (Conventional Commits, scope, allowed types).
  • Plan mode for previewing changes and diff stats before applying.

Quick Start

Invoke the pr-commiter script with a descriptive message and explicit file paths to perform a deterministic commit and PR flow.

Frequently Asked Questions about pr-commiter

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

FAQPage Schema
How do I automate git commits and pull requests with conventional commit policies?

Automating git commits and pull requests requires enforcing branch workflows and explicit path selection during changes. This approach validates conventional commit rules, manages automatic branch creation, and guards against risky operations to ensure deterministic PR integration.

What is deterministic commit flow with explicit file path selection?

Deterministic commit flow restricts changes to explicitly selected file paths, preventing chaotic or accidental commits. It enforces safe branching policies, validates conventional commit standards, and optionally creates pull requests to maintain auditable multi-developer project histories.

Do I need the gh CLI to automate branch creation and PR integration?

Yes, automating branch creation and PR integration requires the gh CLI and git dependencies. These tools enable the workflow to validate config-driven rules, handle optional pushes, and execute automatic PR creation while managing error handling for blocked operations.

Can I preview file changes and diff stats before applying a git commit?

Yes, you can preview file changes and diff stats before applying a git commit using plan mode. This feature allows developers to review explicit path selections and validate conventional commit policies before executing the actual deterministic commit and PR flow.

How do I prevent risky git operations in a multi-developer project?

Preventing risky git operations in a multi-developer project requires enforcing strict branch and PR policies during commits. By restricting changes to explicit file paths and validating config-driven rules, the workflow guards against unauthorized or dangerous repository modifications.

What are the limitations of automating PR creation with conventional commits?

Limitations of automating PR creation include potential error handling for blocked operations and dependency on config-driven rules for scope and allowed types. The workflow requires explicit path selection and cannot process implicit or unguarded file changes.