Contact
Development

Git Workflow

Git workflow best practices for teams and CI/CD pipelines. Covers Git Flow, GitHub Flow, Trunk-based development, Conventional Commits, pull request workflows, and GitHub Actions integration. By Netresearch.

Latest release v1.40.0

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace 
    /plugin install git-workflow@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection 
    npx skills add https://github.com/netresearch/git-workflow-skill

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from skills.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package 
    composer require netresearch/git-workflow-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source 
    composer skills:add netresearch/git-workflow-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.skills.lock. Runtime dependencies remain separate.

What you can do with it

  • Branching Strategies: Git Flow (feature/release/hotfix branches), GitHub Flow (simple feature branches), trunk-based development, release management patterns
  • Commit Conventions: Conventional Commits standard, semantic versioning integration, commit message best practices, atomic commit patterns
  • Collaborative Workflows: Pull request best practices, code review processes, merge strategies (merge, squash, rebase), conflict resolution patterns
  • CI/CD Integration: GitHub Actions workflows, GitLab CI patterns, branch protection rules, automated versioning
  • Git Hooks: Pre-commit hooks for linting and testing, commit message validation
  • Advanced Operations: Interactive rebase, cherry-picking, stashing, reflog recovery

What you get back

  • Branch, commit, hook or pull-request workflow changes, with review and CI status evidence for the requested Git task.

What it expects in your project

Check the source README for current examples, requirements and limitations. Open full README

Tags

  • development
  • devops