commit

Automate Git commits and pushes with explicit user approval.

Updated May 22, 2025
One-click install
npx skills add https://github.com/curtjen/.gir --skill commit-curtjen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/curtjen/.gir/tree/main/skills/commit
Command: npx skills add https://github.com/curtjen/.gir --skill commit-curtjen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents accidental commits by requiring explicit user confirmation for both the commit message and the push action, reducing mistakes in collaborative workflows.

Core Features & Use Cases

  • Interactive confirmation: prompts for a commit message and requires user approval before committing.
  • Push guardrails: asks for push confirmation with target branch and remote before executing.
  • Safe workflow: ensures changes are reviewed and pushed only after explicit consent when working with teammates.

Quick Start

Draft a concise commit message, display it to the user for confirmation, and only stage, commit, and push after getting explicit approval.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I prevent accidental git commits and pushes in a collaborative workflow?

You can prevent accidental git commits by using a workflow that requires explicit user approval for the commit message and the push action, ensuring changes are reviewed before execution.

How do I require user confirmation before a git push to a remote branch?

To require user confirmation before a git push, implement a guardrail that asks for push confirmation with the target branch and remote, executing only after explicit consent is given.

Can I draft a commit message and stage files only after user approval?

Yes, you can draft a commit message, display it for confirmation, and only stage, commit, and push the changes after receiving explicit user approval.

What is a safe git workflow for reviewing changes before committing?

A safe git workflow ensures changes are reviewed and pushed only after explicit consent by prompting for a commit message, confirming the commit, and asking for push approval with the target branch and remote.

Does an automated git workflow back off if push consent is not given?

Yes, an automated git workflow backs off when consent is not given, ensuring that no commits or pushes are executed without explicit user approval.