git-workflow

Validate Git commits, pull requests, and branches against Conventional Commits and branch-safety rules.

9|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Unson-LLC/brainbase --skill git-workflow-unson-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Unson-LLC/brainbase/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/Unson-LLC/brainbase --skill git-workflow-unson-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces Brainbase's Git workflow by ensuring commits and merges conform to governance rules, reducing history drift and improving traceability.

Core Features & Use Cases

  • Conventional Commits enforcement: validates commit messages follow the type(scope): summary pattern.
  • Decision-capture validation: ensures decisions and rationale are recorded alongside changes for future reference.
  • Branch safety checks: prevents direct commits to main/master and guides proper merge workflows.

Quick Start

Use the git-workflow skill to validate a sample commit message such as 'feat(auth): add OAuth login' and verify it adheres to Conventional Commits, while also checking branch-safety constraints.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce Conventional Commits format for git commit messages?

To enforce Conventional Commits, this skill automatically validates that git commit messages follow the type(scope): summary pattern, ensuring proper type and scope formatting before changes are merged into your project history.

How do I prevent direct commits to main or master branches?

To prevent direct commits to main or master branches, this skill applies branch safety checks that block unauthorized pushes and guide developers toward proper merge workflows and session-based branching rules.

What is decision capture in a git workflow and when is it required?

Decision capture in a git workflow is the practice of recording decisions and rationale alongside code changes. This skill requires decision fields to be documented within commits and pull requests to meet project governance and traceability requirements.

How do I validate a pull request for branch safety and commit format?

You validate a pull request by running this skill to check both the Conventional Commits format of its messages and its adherence to branch safety constraints, ensuring no direct main commits and proper merge workflows are followed.

Does this git workflow validation tool require any specific dependencies?

No dependencies are required to use this git workflow validation tool. It operates as a standalone skill to enforce commit message patterns, decision-capture fields, and branch protection rules without external packages.

Why does my commit fail governance checks when pushing to a protected branch?

Your commit fails governance checks because this skill enforces branch safety rules that prevent direct commits to main or master, requiring you to use proper session-based branching and merge workflows instead.