git-workflow

Guide Git branching, merging, and conflict resolution for collaborative development.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill git-workflow-thalesandrades
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ThalesAndrades/forumfoup2026/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/ThalesAndrades/forumfoup2026 --skill git-workflow-thalesandrades

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill clarifies complex Git workflows, enabling teams to coordinate code changes smoothly and prevent merge conflicts.

Core Features & Use Cases

  • Guided Workflow Selection: Helps users choose between GitHub Flow, Trunk-Based Development, and GitFlow based on project needs.
  • Best Practice Instructions: Provides step-by-step guidance on branching, merging, rebasing, and resolving conflicts.
  • Use Case: A developer needs to implement a new feature, update their branch, and prepare a pull request efficiently, avoiding common pitfalls.

Quick Start

Instruct the AI to explain how to rebase a feature branch onto the latest main branch before creating a pull request.

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 resolve Git merge conflicts before creating a pull request?

To resolve Git merge conflicts, you should rebase your feature branch onto the latest main branch and follow step-by-step conflict resolution instructions to ensure a clean project history before opening a pull request.

How do I choose between GitFlow, GitHub Flow, and Trunk-Based Development for my project?

Choosing a branching strategy depends on your project needs: guided workflow selection helps you compare GitFlow, GitHub Flow, and Trunk-Based Development to coordinate code changes and prevent merge conflicts effectively.

How do I rebase a feature branch onto the latest main branch?

To rebase a feature branch, instruct the AI to explain the step-by-step rebasing process onto the latest main branch, which helps maintain a clean project history and avoid common pitfalls during collaborative development.

When do I need to use specific branching conventions for collaborative development?

You need branching conventions for collaborative development when coordinating code changes across a team, ensuring adherence to best practices for code reviews and release management to maintain a clean project history.

Why does my team frequently encounter merge conflicts during version control?

Frequent merge conflicts often occur without effective version control workflows; implementing guided branching strategies and best practice instructions for merging and rebasing helps teams coordinate smoothly and prevent conflicts.

Does this Git workflow guidance work for both feature updates and release management?

Yes, this Git workflow guidance covers both feature implementation and release management, providing best practices for branching, merging, and code reviews to maintain clean project history across collaborative development.