git-workflow

Document Git branching strategies, merge rules, and commit conventions.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill git-workflow-ayub-khan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Ayub-Khan/immortal_agent_swarm/tree/main/.agents/skills/git-workflow
Command: npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill git-workflow-ayub-khan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git projects often suffer from unclear branching, merge conflicts, and inconsistent histories across teams. This skill provides structured, battle-tested branching strategies (GitFlow, GitHub Flow, trunk-based development), clear merge and rebase guidelines, and standardized commit messaging to keep history clean and collaboration efficient.

Core Features & Use Cases

  • Branching strategies: GitFlow, GitHub Flow, and trunk-based development with guidance on when to use each.
  • Merge, rebase, and conflict resolution: step-by-step practices to minimize integration pain and preserve a clean history.
  • Commit message standards and PR workflows: conventions that improve reviewability and traceability across teams.
  • Use Case: Ideal for teams that need reliable release processes, collaborative code reviews, and scalable version control across multiple contributors.

Quick Start

Define and apply a Git workflow by selecting a branching strategy, configuring merge/rebase practices, and enforcing consistent commit messages.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I establish a structured Git workflow for my team?

To establish a structured Git workflow, select a branching strategy like GitFlow, GitHub Flow, or trunk-based development, then configure merge and rebase rules alongside standardized commit messages to ensure clean history and efficient collaboration.

What is the best way to resolve merge conflicts during a Git rebase?

The best way to resolve merge conflicts during a Git rebase is to follow step-by-step conflict resolution practices that minimize integration pain, preserve a clean project history, and include recovery procedures for safety.

When should I choose GitFlow versus trunk-based development?

Choose GitFlow versus trunk-based development based on your release process needs: GitFlow supports structured release branches for scheduled deployments, while trunk-based development enables fast integration for continuous delivery.

How do I enforce consistent commit messages and PR workflows across contributors?

To enforce consistent commit messages and PR workflows, codify commit conventions and review standards that improve traceability and reviewability, ensuring scalable version control across multiple team contributors.

Can I use these Git branching strategies for projects of all sizes?

Yes, you can use these Git branching strategies for projects of all sizes. The guidelines are applicable to any project needing reliable release processes, collaborative code reviews, and scalable version control.

Why does my team keep getting inconsistent Git histories after merges?

Inconsistent Git histories after merges usually happen without clear merge and rebase guidelines. Codifying concrete commands and standardized commit conventions prevents unclear branching and keeps history clean.