git-team-workflow

Guide Git branching, commits, and PR reviews for team workflows.

7|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Jonathan0823/opencode-config --skill git-team-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-team-workflow
Source: https://github.com/Jonathan0823/opencode-config/tree/main/skills/git-team-workflow
Command: npx skills add https://github.com/Jonathan0823/opencode-config --skill git-team-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides clear guidelines for implementing effective Git workflows, branching strategies, and team collaboration practices to reduce confusion and bottlenecks in software projects.

Core Features & Use Cases

  • Branching strategies: Guidance for GitFlow, GitHub Flow, and trunk-based development to structure work across releases.
  • Commit & PR practices: Conventional commits, PR templates, and review processes to ensure traceable, high-quality changes.
  • Team collaboration & governance: Guidelines for coordinating reviews, releases, and branch naming in teams of varying sizes.

Use Case: When starting a new project, apply these patterns to establish a consistent branching model, commit discipline, and PR workflow, enabling smoother collaboration and faster releases.

Quick Start

Start by installing Git, cloning the repository, and creating a feature branch from the chosen base branch. Example: git checkout develop; git pull origin develop; git checkout -b feature/new-feature. Then commit using conventional commits and open a PR following the template guidelines.

Frequently Asked Questions about git-team-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 a team?

The best way to manage Git branching strategies is to adopt a structured workflow like GitFlow, GitHub Flow, or trunk-based development. These models coordinate feature branching, enforce PR reviews, and streamline release coordination.

How do I enforce conventional commits and branch naming in pull requests?

To enforce conventional commits and branch naming in pull requests, establish a structured code review process with PR templates. This ensures traceable, high-quality changes and consistent commit discipline across the team.

Does trunk-based development work for coordinating releases in small teams?

Yes, trunk-based development works for coordinating releases in small teams by promoting frequent integrations into a single base branch. It reduces merge conflicts and accelerates release cycles compared to long-lived feature branches.

How do I create a feature branch and open a pull request using GitHub Flow?

To create a feature branch and open a pull request using GitHub Flow, checkout your base branch, pull the latest updates, and create a feature branch. Commit your changes using conventional commits, then open a PR using the template guidelines.

When should I use GitFlow instead of GitHub Flow for project releases?

Use GitFlow instead of GitHub Flow when your project requires structured release coordination with distinct release and hotfix branches. GitFlow supports versioned releases, whereas GitHub Flow is optimized for continuous deployment.

Why do we need conventional commits in code review workflows?

Conventional commits are needed in code review workflows to provide a standardized commit history. They ensure traceable changes, simplify automated release notes generation, and help reviewers understand the context of pull requests.