git-workflow

Enforce branch creation, conventional commits, and PR-based reviews in Git workflows.

2|Updated Dec 13, 2025

Search Tags:#git #workflow #branching #pull-request #version-control #conventional-commits

Ready to run

npx skills add https://github.com/saavy1/sb --skill git-workflow-saavy1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/saavy1/sb/tree/main/docs/.claude/skills/git-workflow
Command: npx skills add https://github.com/saavy1/sb --skill git-workflow-saavy1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents sometimes bypass standardized Git practices, risking main branch integrity and inconsistent workflows. This skill provides clear guidelines to enforce safe branching, naming, and review processes.

Core Features & Use Cases

Branch Strategy: Enforces creating feature/fix branches off main and prevents direct commits to main.
Branch Naming: Uses prefixes like feat/, fix/, refactor/, docs/, chore/ to improve traceability.
Workflow & Commits: Encourages conventional commit messages and PR-based reviews to ensure code quality and collaboration.
Use Cases: Ideal for AI-assisted development, code review automation, and multi-team collaboration.

Quick Start

Switch to main, pull the latest changes, create a properly named feature branch (for example feat/your-feature), and begin work.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce a standardized Git workflow for AI-assisted development?▼

You can enforce a standardized Git workflow by creating feature or fix branches off the main branch before starting work. This prevents direct commits to main and ensures code changes go through a PR-based review process.

What is the best way to prevent AI agents from committing directly to the main branch?▼

Preventing direct commits to main requires a main guard that enforces creating properly named branches like feat/ or fix/ before any work begins. This maintains branch integrity and ensures all changes are reviewed via pull requests.

How do conventional commits improve version control in a team workflow?▼

Conventional commits improve version control by standardizing commit messages across feature work, bug fixes, and documentation tasks. This naming convention enhances traceability and supports consistent, reproducible Git workflows during PR-based reviews.

Does this Git branching workflow support bug fixes and documentation updates?▼

Yes, the Git branching workflow applies to feature work, bug fixes, and documentation tasks. It uses specific branch prefixes like fix/ and docs/ to categorize changes and maintain traceability across the version control process.

Why should I use branch prefixes like feat/ and refactor/ in version control?▼

Using branch prefixes like feat/, fix/, refactor/, docs/, and chore/ improves traceability in version control. It clearly categorizes the purpose of each branch, ensuring reproducible Git workflows and organized PR-based reviews for teams.