Skill

git-workflows

Git workflows: trunk-based development vs GitFlow, Conventional Commits specification, PR templates, branch protection rules, merge strategies (squash vs merge vs rebase), interactive rebase for clean history, git bisect for debugging, monorepo patterns. Use when setting up team git workflow, writing commit messages, reviewing PR process.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Choosing between trunk-based development and GitFlow

Supporting Assets

references/branching-strategies.mdreferences/conventional-commits.mdreferences/monorepo-strategies.md

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

git-workflows

Core Principles

Trunk-based development for speed — long-lived branches cause merge hell; merge to main daily

Conventional Commits enable automation — feat:, fix:, chore: → automatic semantic versioning and changelogs

Squash merge for feature branches — one commit per feature on main = clean, bisectable history

Feature flags over long branches — merge incomplete code behind a flag; avoid 3-week branches

Branch protection is non-negotiable — no direct push to main; required reviews and CI passing

References available

references/branching-strategies.md — trunk-based workflow, branch naming conventions, PR template, branch protection rules, git bisect, interactive rebase

references/conventional-commits.md — full type reference, breaking changes, examples, semantic versioning trigger rules

references/monorepo-strategies.md — Turborepo, Nx, affected package detection, shared commit scopes

Git Workflows

When to Use This Skill

Choosing between trunk-based development and GitFlow
Writing Conventional Commits for automatic changelogs
Setting up branch protection and PR review requirements
Cleaning up commit history before merging
Debugging regressions with git bisect

Core Principles

Trunk-based development for speed — long-lived branches cause merge hell; merge to main daily
Conventional Commits enable automation — feat:, fix:, chore: → automatic semantic versioning and changelogs
Squash merge for feature branches — one commit per feature on main = clean, bisectable history
Feature flags over long branches — merge incomplete code behind a flag; avoid 3-week branches
Branch protection is non-negotiable — no direct push to main; required reviews and CI passing

References available

references/branching-strategies.md — trunk-based workflow, branch naming conventions, PR template, branch protection rules, git bisect, interactive rebase
references/conventional-commits.md — full type reference, breaking changes, examples, semantic versioning trigger rules
references/monorepo-strategies.md — Turborepo, Nx, affected package detection, shared commit scopes