git-governance

Enforces Git Flow branching and Conventional Commits conventions for AI-driven development tasks.

Updated May 21, 2025
One-click install
npx skills add https://github.com/albertmartorell1975/MeteoMartoCompose --skill git-governance-albertmartorell1975
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-governance
Source: https://github.com/albertmartorell1975/MeteoMartoCompose/tree/main/.agents/skills/git-governance
Command: npx skills add https://github.com/albertmartorell1975/MeteoMartoCompose --skill git-governance-albertmartorell1975

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams working with AI coding agents often end up with inconsistent branch names, mixed-layer commits, and unreviewed changes pushed to the wrong branches. This Skill enforces a strict Git Flow branching model and commit conventions so every AI-assisted change lands in the correct branch with a clean, reviewable history. ## Core Features & Use Cases - Branch Type Diagnosis: Automatically determines whether a task requires a feature, bugfix, hotfix, or release branch, and selects the correct parent branch (develop, main, release, or an existing feature branch). - Conventional Commits with Module Scopes: Generates atomic, layer-specific commit messages in the format <type>(<module>): [ID] <subject>, following the Domain -> Data -> UseCase -> UI flow. - Human Review Gate: Prohibits autonomous commit, push, and merge operations, requiring the user to review and commit changes manually. - Use Case: When an AI agent implements a new feature like a high-temperature push notification, it creates feature/MM-01-high-temp-notification from develop, stages files as it works, and prepares atomic commits for user review. ## Quick Start Ask the agent to start a new feature task and it will diagnose the repository state, propose the correct branch, and prepare conventional commits for your review.

Frequently Asked Questions about git-governance

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

FAQPage Schema
How do I enforce Git Flow branching with an AI coding agent?▼

Define explicit branching rules that map task types to parent branches: features from develop, hotfixes from main, and bugfixes from wherever the affected code lives. The agent diagnoses the repository state with git commands before creating any branch.

What is the Conventional Commits format with module scopes?▼

The format is `<type>(<module>): [ID] <subject>`, such as `feat(data): [MM-123] implement firebase remote config source`. Types include feat, fix, docs, style, refactor, test, and chore, with the module indicating the affected architecture layer.

Can AI agents commit and push code autonomously?▼

Under this governance model, agents are prohibited from running git commit, push, or merge autonomously. They stage files and prepare commit messages, but the user performs the actual commit after reviewing every modification.

How do I choose the parent branch for a bugfix in Git Flow?▼

The parent depends on where the bug exists: branch from develop for bugs in the current dev cycle, from a release branch for bugs found during release testing, or from the specific feature branch if the bug is localized to ongoing work.

Why should commits be atomic and layer-specific in Clean Architecture?▼

Layer-specific commits keep Domain, Data, UseCase, and UI changes separated, making reviews easier and history cleaner. Sequential commits following the Domain to UI flow let reviewers trace implementation logic step by step.