git-workflow

Standardize Git branching, worktree management, and collaboration patterns.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ps-carvalho/cortex-agents --skill git-workflow-ps-carvalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ps-carvalho/cortex-agents/tree/main/.opencode/skills/git-workflow
Command: npx skills add https://github.com/ps-carvalho/cortex-agents --skill git-workflow-ps-carvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git branching strategies, worktree management, and collaborative development workflows are provided to help teams coordinate and accelerate software delivery.

Core Features & Use Cases

  • Standardized branching patterns (feature, bugfix, hotfix, release) to align teams.
  • Worktree management for parallel development streams without duplicating repos.
  • Protected branches and commit conventions to enforce code quality.
  • Pull request guidance and workflow orchestration to speed reviews.

Quick Start

Ask the AI to configure a Git workflow with defined branch types, worktree setup, and PR guidelines for your repository.

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 patterns for parallel feature work and hotfixes?

Standardize Git branching by defining specific branch types like feature, bugfix, hotfix, and release. This aligns teams on parallel development streams, ensuring structured coordination and accelerating software delivery across multi-branch projects.

How does Git worktree management help with parallel development streams?

Git worktree management enables parallel development streams without duplicating repositories. It allows you to work on multiple branches simultaneously, improving development flow and preventing workspace collisions during coordinated team reviews.

What's the best way to enforce commit conventions and protected branches in version control?

The best way to enforce commit conventions and protected branches is by applying standardized workflow patterns. This regulates code quality by preventing direct commits to critical branches and ensuring uniform commit histories.

Can I use this Git workflow orchestration for multi-branch projects with coordinated team reviews?

Yes, this Git workflow orchestration is designed specifically for multi-branch projects. It coordinates parallel feature work and hotfixes while providing pull request guidance to speed up and structure team reviews.

Why do I need pull request guidance for collaborative Git workflows?

Pull request guidance is needed to streamline collaborative Git workflows and speed up reviews. It provides structured patterns for submitting, reviewing, and merging code changes, ensuring quality control across coordinated team efforts.

When do I need to configure standardized Git workflow patterns for my repository?

You need to configure standardized Git workflow patterns when your repository requires coordinated team collaboration, parallel feature development, or structured hotfix and release management to maintain code quality and accelerate delivery.