skills.rest
AndreaCadonna
AndreaCadonnaCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Standardize Git workflows with trunk-based branching and conventional commits.

Updated Mar 8, 2026
Search Tags:#git#workflow#branching#commits#code-review#pull-request#branch-protection
One-click install
npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill git-workflow-andreacadonna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/AndreaCadonna/sbobuz-web-game-app/tree/main/skills/git-workflow
Command: npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill git-workflow-andreacadonna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git workflows across teams by providing a shared set of guidelines for branching, commits, PRs, and reviews, reducing conflicts and history chaos.

Core Features & Use Cases

  • Branching strategy guidelines including trunk-based development and main as deployable.
  • Commit message conventions to maintain a clean history and clear intent.
  • Pull request workflow, review patterns, and branch protection rules to ensure code quality.
  • Merge strategies and version tagging to support releases and traceability.
  • Branch naming rules to promote consistency across the codebase.

Quick Start

Explain how to create a feature branch from main, follow the commit message conventions, open a PR, and merge with branch protection rules.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git workflows across my team?▼

Standardize Git workflows by enforcing trunk-based branching from main, conventional commit message formats, PR gating with code reviews, and release tagging to maintain history consistency and project stability across collaborative teams.

What is trunk-based branching and how does it manage main branch stability?▼

Trunk-based branching is a Git workflow strategy where developers branch from main for features and merge back quickly. It keeps main deployable by enforcing pull request gating, code reviews, and branch protection rules before merges.

How do I write conventional commit messages for a clean Git history?▼

Conventional commit messages follow a standardized format to maintain clear intent and a clean Git history. They enforce structured prefixes for features, fixes, and breaks, supporting traceability and automated version tagging during releases.

How do I set up branch protection rules for pull request gating?▼

Set up branch protection rules by enforcing pull request workflows that require code reviews before merging into main. This ensures quality by gating merges, standardizing naming conventions, and applying consistent merge strategies.

Can I use this Git workflow for collaborative software projects at scale?▼

Yes, this Git workflow is designed for collaborative software projects at scale. It reduces conflicts and history chaos by standardizing branch naming, merge strategies, and version tagging across multiple team members.

What is the best way to name feature branches and tag releases in Git?▼

The best way to name feature branches and tag releases is by following standardized branch naming rules and version tagging conventions. This promotes codebase consistency, supports reliable releases, and maintains traceability for collaborative projects.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
RoxabiRoxabi
9

promote

Automate staging-to-main branch promotion with pre-flight checks, versioning, and pull request creation.

Official
Advanced
thesammykinsthesammykins

code-quality-gates

Enforces predefined quality gates for code reviews and merges.

Community
Advanced
autohandaiautohandai
10

git-workflow-mastery

Configure Git branching strategies and conventional commit workflows.

Official
Advanced