From git-workflow
Guides Git branching, Conventional Commits, PR workflows, CI/CD integration, signed merges, conflict resolution, releases, and git hooks setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-workflow:git-workflowThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **No direct push to main** — always open a PR.
checkpoints.yamlevals/evals.jsonreferences/advanced-git.mdreferences/branching-strategies.mdreferences/ci-cd-integration.mdreferences/claude-code-hooks.mdreferences/code-quality-tools.mdreferences/commit-conventions.mdreferences/git-hooks-setup.mdreferences/github-releases.mdreferences/merge-gate-watcher.mdreferences/no-editorializing.mdreferences/pull-request-workflow.mdreferences/spec-cleanup.mdscripts/spec-cleanup-guard.shscripts/verify-git-workflow.shreferences/pull-request-workflow.md.~/.claude/skills/, ~/.claude/plugins/cache/, **/.bare/**) — always the repo worktree, verified by pwd.--force-with-lease — never plain --force.add → commit → fetch → rebase → push. Dirty tree aborts rebase.references/no-editorializing.md.See references/pull-request-workflow.md for merge-gate and atomic-commit patterns.
Load on demand:
| Reference | Content Triggers |
|---|---|
references/branching-strategies.md | Branching models, Git/GitHub Flow, trunk-based, protection |
references/commit-conventions.md | Conventional commits, DCO sign-off, semantic versioning, commitlint |
references/pull-request-workflow.md | PR create/review/merge, threads, strategies, CODEOWNERS, signed rebase |
references/ci-cd-integration.md | GitHub Actions, GitLab CI, semantic release, deployment |
references/advanced-git.md | Rebase, cherry-pick, bisect, stash, worktrees, reflog, recovery |
references/github-releases.md | Immutable releases, --latest=false, multi-branch |
references/git-hooks-setup.md | Hook frameworks, detection, hooks per stage |
references/claude-code-hooks.md | Claude Code settings.json hooks — merge gate, cache-path rejection, auto-lint |
references/code-quality-tools.md | shellcheck, shfmt, git-absorb, difftastic |
references/merge-gate-watcher.md | Merge-driver loop, check taxonomy, stale-SHA rerun, review-bot rounds |
references/spec-cleanup.md | Keep planning artifacts off the base branch; guard + capture-to-ADR |
references/no-editorializing.md | Writing without self-praise or narrating the expected |
<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
Detect hooks first:
ls lefthook.yml .lefthook.yml captainhook.json .pre-commit-config.yaml .husky/pre-commit 2>/dev/null || echo "No hooks"
Install: lefthook install | composer install | npm install | pre-commit install
--latest=false from non-default branches.git pull BEFORE gh release create.Before merging: threads resolved, CI green (incl. annotations), rebased, signed. Rebase-only + signed: git merge --ff-only.
./scripts/verify-git-workflow.sh /path/to/repository
Contributing: https://github.com/netresearch/git-workflow-skill
npx claudepluginhub netresearch/claude-code-marketplace --plugin git-workflowGuides teams in choosing a branching strategy (trunk-based, GitHub Flow, Git Flow, GitLab Flow), defining commit conventions (Conventional Commits), setting up PR workflows, managing releases, and establishing git standards.
Guides Git operations including conventional commits, PR formatting, and a dual-gate CI workflow. Use for version control tasks.
Guides git workflows including trunk-based vs GitFlow, Conventional Commits, PR templates, branch protection, squash/rebase merges, interactive rebase, bisect, monorepos. Use for team setup, commit messages, PR reviews.