git-workflow

Guide Git branching strategies, commit conventions, and merge/rebase decisions.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill git-workflow-dhruvinrsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/80-collaboration/git-workflow
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill git-workflow-dhruvinrsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines version control by establishing clear guidelines for branching, committing, merging, and resolving conflicts, ensuring a clean and manageable project history.

Core Features & Use Cases

  • Branching Strategies: Recommends models like GitFlow or Trunk-Based Development.
  • Commit Conventions: Enforces formats like Conventional Commits for readable logs.
  • Merge/Rebase Decisions: Guides optimal strategies for integrating changes.
  • Conflict Resolution: Provides steps for efficiently resolving merge conflicts.
  • Use Case: A team struggling with messy Git history can use this Skill to adopt a consistent branching model and commit message format, making code reviews and debugging significantly easier.

Quick Start

Configure git-workflow to establish a branching strategy and commit convention for the repository at 'https://github.com/example/repo.git'.

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 manage Git branching strategies for team collaboration?

Merge conflicts are resolved by following standardized conflict resolution protocols that guide optimal merge and rebase decisions. This Skill provides steps for efficiently resolving conflicts, ensuring that team collaboration maintains a clean and manageable project history.

How do I enforce Conventional Commits for readable version control logs?

You enforce Conventional Commits by applying standardized commit conventions and Git hook configurations. This establishes clear guidelines for committing, ensuring readable logs that satisfy requirements for standardized workflows and make code reviews easier.

When do I need to use a rebase instead of a merge in Git?

You need to use rebase instead of merge when integrating changes requires a linear project history. This Skill guides optimal merge and rebase decisions based on your specific scenario, ensuring effective version control and maintaining clean history.

Does this Git workflow approach work for release management and maintaining project history?

Yes, this Git workflow approach works for release management by addressing scenarios involving team collaboration and maintaining a clean project history. It establishes clear guidelines for branching, committing, merging, and resolving conflicts to ensure a manageable repository.