Use when establishing branching strategies, implementing Conventional Commits, creating or reviewing PRs, resolving PR review comments, merging PRs (including CI verification, auto-merge queues, and post-merge cleanup), managing PR review threads, merging PRs with signed commits, handling merge conflicts, creating releases, or integrating Git with CI/CD.
From git-workflownpx claudepluginhub netresearch/claude-code-marketplace --plugin git-workflowThis skill is limited to using the following tools:
checkpoints.yamlevals/evals.jsonreferences/advanced-git.mdreferences/branching-strategies.mdreferences/ci-cd-integration.mdreferences/code-quality-tools.mdreferences/commit-conventions.mdreferences/git-hooks-setup.mdreferences/github-releases.mdreferences/pull-request-workflow.mdscripts/verify-git-workflow.shDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Expert patterns for Git version control: branching, commits, collaboration, and CI/CD.
Load references on demand based on the task at hand:
| Reference | Content Triggers |
|---|---|
references/branching-strategies.md | Branching model, Git Flow, GitHub Flow, trunk-based, branch protection |
references/commit-conventions.md | Commit messages, conventional commits, semantic versioning, commitlint |
references/pull-request-workflow.md | PR create/review/merge, thread resolution, merge strategies, CODEOWNERS, signed commits + rebase |
references/ci-cd-integration.md | GitHub Actions, GitLab CI, semantic release, deployment |
references/advanced-git.md | Rebase, cherry-pick, bisect, stash, worktrees, reflog, submodules, recovery |
references/github-releases.md | Release management, immutable releases, --latest=false, multi-branch |
references/git-hooks-setup.md | Hook frameworks, detection, recommended hooks per stage |
references/code-quality-tools.md | shellcheck, shfmt, git-absorb, difftastic |
<type>[scope]: <description>
Types: feat (MINOR), fix (PATCH), docs, style, refactor, perf, test, build, ci, chore, revert
Breaking change: Add ! after type or BREAKING CHANGE: in footer.
feature/TICKET-123-description
fix/TICKET-456-bug-name
release/1.2.0
hotfix/1.2.1-security-patch
Before first commit, detect and install hooks:
ls lefthook.yml .lefthook.yml captainhook.json .pre-commit-config.yaml .husky/pre-commit 2>/dev/null || echo "No hooks"
Install: lefthook.yml -> lefthook install | captainhook.json -> composer install | .husky/ -> npm install | .pre-commit-config.yaml -> pre-commit install
--latest=false when releasing from non-default branches (LTS, maintenance, hotfix).git pull on main -- verify BEFORE gh release create.Before merging: all threads resolved, CI checks green (including annotations), branch rebased, commits signed (if required). For signed commits + rebase-only repos, use local git merge --ff-only.
./scripts/verify-git-workflow.sh /path/to/repository
Contributing: https://github.com/netresearch/git-workflow-skill