git

Verify the work branch and require approval before executing Git commits.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill git-tacuchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/Tacuchi/agent-workflow-cli/tree/main/skills/w/roles/git
Command: npx skills add https://github.com/Tacuchi/agent-workflow-cli --skill git-tacuchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies the expected work branch before edits and prevents destructive actions without explicit user consent, enabling safer code edits in collaborative environments.

Core Features & Use Cases

  • Verify the work branch against the declared main branch before any write/edit.
  • Propose commits for each dirty source and execute them only after explicit user approval, one at a time.
  • Read-only operations such as status, log and diff are permitted; destructive actions (push, reset, rebase, etc.) require explicit user consent.
  • Use case: review code changes safely in a multi-contributor project and ensure commits are deliberate and auditable.

Quick Start

Enable git-safe mode for a project and approve the proposed commits before any write operations.

Frequently Asked Questions about git

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

FAQPage Schema
How do I prevent accidental git commits on the wrong branch?

To prevent accidental git commits on the wrong branch, this Skill verifies your active work branch against the declared main branch before any edits are applied. It enforces safe defaults by blocking writes until branch validation succeeds.

Can I review code changes in git before they are committed?

Yes, you can review code changes before they are committed. The Skill proposes commits for each dirty source file and executes them one at a time, only after receiving your explicit approval for each specific change.

Does this git workflow allow read-only operations like log and diff?

This git workflow fully permits read-only operations such as checking status, viewing logs, and running diffs. Destructive actions like push, reset, and rebase require explicit user consent before execution.

How do I enforce safe defaults for git push, merge, and rebase operations?

To enforce safe defaults for git push, merge, and rebase operations, the Skill requires explicit user consent before executing any destructive actions. This prevents accidental history rewrites or unauthorized pushes in collaborative environments.

What is the best way to ensure commits are deliberate in a multi-contributor project?

The best way to ensure commits are deliberate in a multi-contributor project is using a workflow that proposes commits per source file and executes them individually after explicit user approval. This makes all changes auditable.