git-workflow

Design Git workflows and CI/CD patterns with branching models and conventional commits.

5|Updated Oct 27, 2025

Search Tags:#git #branching #github-actions #ci-cd #workflows #conventional-commits

Ready to run

npx skills add https://github.com/jbabin91/autocomplete-rs --skill git-workflow-jbabin91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jbabin91/autocomplete-rs/tree/main/.agents/skills/git-workflow
Command: npx skills add https://github.com/jbabin91/autocomplete-rs --skill git-workflow-jbabin91

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design teams with a robust, repeatable set of Git workflows, branching models, commit conventions, and CI/CD patterns to improve collaboration and delivery velocity.

Core Features & Use Cases

Branching strategies (Git Flow, GitHub Flow, One-Flow) to suit release cadences
Conventional commits and semantic versioning guidance for clean history
CI/CD automation with reusable workflows and template actions
Repository hygiene practices like stacking PRs, issue templates, and branch pruning
Real-world scenarios: migrating from ad-hoc processes to trunk-based development in a SaaS team

Quick Start

Describe your project's needs and I will design a tailored Git workflow with branches, commits, and CI patterns.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

What is the best way to design a scalable Git workflow for a growing team?▼

The best way to design a scalable Git workflow is to adopt a branching model like Git Flow, GitHub Flow, or One-Flow that matches your release cadence while enforcing conventional commits and CI gating for clean history.

How do I standardize commit messages and automate semantic versioning in CI/CD?▼

You can standardize commit messages by adopting conventional commits, which enables automated semantic versioning and clean Git history when integrated into your CI/CD automation and reusable GitHub Actions workflows.

How do I migrate from an ad-hoc branching process to trunk-based development?▼

Migrating to trunk-based development requires applying repository hygiene practices like branch pruning, stacking PRs, and implementing CI gating to enforce standardized commit messages and reusable workflows during the transition.

Can I use GitHub Actions to enforce repository hygiene and environment gating?▼

Yes, you can use reusable GitHub Actions workflows to enforce repository hygiene, implement environment gating, and automate PR hygiene for your projects adopting branching models and CI/CD patterns.

What is the difference between Git Flow, GitHub Flow, and One-Flow branching strategies?▼

Git Flow, GitHub Flow, and One-Flow differ in their release cadence support and branch structure, with each model offering distinct advantages for trunk-based development migration and team collaboration velocity.