git-workflow

Standardize Git branching, commit conventions, and PR workflows across teams.

51|13|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/netresearch/claude-code-marketplace --skill git-workflow-netresearch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/netresearch/claude-code-marketplace/tree/main/skills/git-workflow
Command: npx skills add https://github.com/netresearch/claude-code-marketplace --skill git-workflow-netresearch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, and includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill codifies best practices for Git workflows, including branching strategies, Conventional Commits, PR review processes, and CI/CD integration.

Core Features & Use Cases

  • Branching Strategies: Git Flow, GitHub Flow, trunk-based development.
  • Commit Conventions: Conventional Commits with guidance on message structure.
  • CI/CD Integration: PR reviews, automated tests, and release practices.

Quick Start

Use the Git Workflow Skill to establish consistent branching, commit, and PR practices across a project.

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 workflow practices across my team?

Standardize Git workflow practices by implementing branching strategies, commit conventions, and PR processes encoded in your repository. This Skill provides patterns for Git Flow, GitHub Flow, and trunk-based development, along with CI/CD integration templates that enforce consistent practices across team members.

What is Conventional Commits and how does it improve collaboration?

Conventional Commits is a specification for structuring commit messages with type, scope, and description. It improves collaboration by making commit history readable, enabling automated changelog generation, and clarifying intent for code reviews and CI/CD pipelines.

How do I set up branching strategies like Git Flow or trunk-based development?

Set up branching strategies by defining branch naming conventions, protection rules, and merge workflows in your repository. This Skill provides scripts and references for implementing Git Flow (feature/release/hotfix branches), GitHub Flow (main + feature branches), or trunk-based development with automated versioning.

Can I automate PR reviews and release management with CI/CD platforms?

Yes. Automate PR reviews and releases by integrating branch protection, pre-commit hooks, and CI/CD workflows with GitHub Actions or GitLab CI. This Skill includes patterns for automated testing, semantic versioning, and release processes triggered by commit conventions.

What are pre-commit and commit-msg hooks and why do I need them?

Pre-commit and commit-msg hooks are Git hooks that run scripts before commits are saved, enforcing code quality and message format requirements. They prevent non-compliant commits from entering your repository and ensure all commits follow Conventional Commits format and branch naming conventions.

Does this Skill work with GitHub Actions and GitLab CI?

Yes. This Skill includes patterns for both GitHub Actions and GitLab CI, covering PR workflows, automated tests, branch protection, and release management across these CI/CD platforms.