git-workflow

Standardize Git branching, commit, and pull request practices for team workflows.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill git-workflow-richardnpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/richardnpaul/everything-vscode-copilot/tree/main/.github/skills/git-workflow
Command: npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill git-workflow-richardnpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git collaboration for teams can become chaotic without a clear, shared workflow, leading to merge conflicts, inconsistent commit history, and slow onboarding.

Core Features & Use Cases

  • Standardized branching strategies (GitHub Flow, GitFlow, trunk-based development) to align release cycles and CI/CD.
  • Prescribed commit message conventions and PR description templates to improve traceability and reviews.
  • Conflict resolution guidelines and release/tag management to streamline collaboration across multiple contributors.

Quick Start

Create a feature branch from main, implement your change, and open a pull request after passing CI.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git branching and pull request workflows for a growing team?

Standardize Git workflows by defining branching, commit, and PR practices to reduce conflicts and improve traceability across team projects. This covers GitHub Flow, GitFlow, and trunk-based development workflows.

What is the best way to manage merge conflicts and rebase operations across multiple contributors?

Manage merge conflicts and rebase operations by applying prescribed conflict resolution guidelines and release tag management processes. This streamlines collaboration and maintains consistent commit history across contributors.

How do I enforce commit message conventions and PR templates for better traceability?

Enforce commit message conventions and PR templates to improve traceability and code reviews. Standardized metadata requirements ensure consistent formatting across all team contributions and pull requests.

Does this Git workflow support both trunk-based development and GitFlow release cycles?

This Git workflow supports trunk-based development, GitFlow, and GitHub Flow to align release cycles and CI/CD processes. It scales for team projects of varying sizes and workflow preferences.

Why does my team need a standardized Git workflow instead of ad-hoc branching?

A standardized Git workflow prevents chaotic collaboration that leads to merge conflicts, inconsistent commit history, and slow onboarding. Shared practices ensure faster collaboration and clear release tag management.