git-workflow

Enforce branch naming, PR gates, and merge practices in Git workflows.

27|9|Updated Jan 20, 2026

Search Tags:#git #workflow #branching #pull-requests #merge-conflicts #commit-messages

Ready to run

npx skills add https://github.com/sabahattink/antigravity-fullstack-hq --skill git-workflow-sabahattink

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/sabahattink/antigravity-fullstack-hq/tree/main/skills/git-workflow
Command: npx skills add https://github.com/sabahattink/antigravity-fullstack-hq --skill git-workflow-sabahattink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle with chaotic code changes and inconsistent collaboration workflows, leading to misaligned merges and fragile releases.

Core Features & Use Cases

Branching strategy guidance (e.g., GitFlow-style, GitHub Flow) to structure work and isolate features.
Commit message conventions and PR workflow to ensure traceability, code quality, and auditable history.
Conflict resolution practices and merge hygiene to prevent broken builds and reduce review time.
Use Case: A team implements a standard PR-based workflow to land feature branches with required approvals and CI checks.

Quick Start

Follow the example in the skill to implement a standard Git workflow with named branches and PR gates.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

What is a standard Git workflow for managing feature branches and pull requests?▼

A standard Git workflow structures code changes using branching strategies like GitFlow or GitHub Flow, isolating features in named branches that pass through PR review gates and CI checks before a safe merge.

How do I resolve merge conflicts during a pull request?▼

Resolve merge conflicts during a pull request by applying conflict resolution practices and merge hygiene, ensuring divergent changes are reconciled cleanly to prevent broken builds and reduce code review time.

How do I structure Git commit messages for better traceability?▼

Structure Git commit messages by following commit message conventions that enforce traceability and code quality, ensuring an auditable history across software-engineering projects.

What's the best way to enforce branch naming rules and required approvals in Git?▼

Enforce branch naming rules and required approvals by implementing a PR-based workflow with PR review requirements and CI integration, maintaining a production-grade code base through disciplined merge practices.

Does this Git workflow support both GitFlow and GitHub Flow branching strategies?▼

Yes, this Git workflow supports branching strategy guidance for both GitFlow-style and GitHub Flow approaches, allowing teams to structure work and isolate features according to their preferred collaboration model.

Why do I need CI integration for pull requests in a disciplined Git workflow?▼

You need CI integration for pull requests to act as PR gates that validate code quality, enforce safe merge practices, and prevent fragile releases caused by misaligned merges and inconsistent collaboration.