gated-commit

Enforce a controlled commit gate for git write operations.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/vhqtvn/vh-solara --skill gated-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gated-commit
Source: https://github.com/vhqtvn/vh-solara/tree/main/.opencode/skills/gated-commit
Command: npx skills add https://github.com/vhqtvn/vh-solara --skill gated-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or accidental git write operations by routing commits through a controlled gate, so changes are staged, reviewed, and applied only through the approved workflow.

Core Features & Use Cases

  • Commit Gate Enforcement: Blocks direct git mutation commands and requires delegation to the committer flow.
  • Review-Aware Commit Flow: Supports message drafting, review, acquisition, commit, release, and heartbeat refresh for long-running sessions.
  • Safer Team Operations: Useful when multiple agents or workflows may touch the same repository and need consistent write controls.
  • Use Case: When you need to commit a feature branch without bypassing repository safety rules, use this Skill to stage the message file, acquire the gate, and complete the commit through the approved process.

Quick Start

Ask the assistant to prepare a gated commit for your changed files, draft the commit message, and complete the commit using the repository’s enforced commit-gate workflow.

Frequently Asked Questions about gated-commit

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

FAQPage Schema
How do I enforce a review workflow before allowing git commits?

A commit gate blocks direct git write operations and requires routing through a controlled flow involving message file staging, review delegation, and gate acquisition before applying changes to the repository.

How do I safely manage staged commits for long-running agent sessions?

You manage staged commits in long-running agent sessions by using message-file based gate acquisition, heartbeat refresh to maintain session state, and gate-managed release actions to safely finalize repository changes.

Can I prevent accidental git write operations when multiple workflows touch the same repository?

Yes, you can prevent unsafe git write operations by enforcing a controlled commit gate, ensuring multiple agents or workflows follow consistent write controls, staged commits, and review delegation within the same repository.

What is the process to draft and complete a gated commit?

The gated commit process involves staging changed files, drafting a commit message file, acquiring the commit gate, executing the commit through the enforced workflow, and releasing the gate to preserve repository write safety.

Does this commit gate workflow require specific dependencies or components?

This commit gate workflow requires no external dependencies or components, operating as a standalone safety layer that enforces message-file based acquisition, review delegation, and heartbeat refresh for git write operations.

When should I use a controlled commit gate instead of direct git commits?

Use a controlled commit gate instead of direct git commits when performing release coordination, managing long-running agent sessions, or requiring strict write safety and review delegation for repository change management.