Git Workflow Skill

When to Use

• Branching, Conventional Commits; PRs: open, review, resolve threads, merge (CI gate, queues, cleanup)
• Conflicts, rebasing a long-lived branch, splitting a PR, git hooks (incl. worktree installs)
• Not here: releases (github-release); BLOCKED-PR diagnosis (github-project)

Critical Rules (Non-Negotiable)

1. No direct push to main — always open a PR.
2. No merge before all threads resolved (references/pull-request-workflow.md).
3. No squash unless asked — preserves atomic commits, signatures, bisection.
4. No "tested/verified/working" without pasted command output — else say so.
5. No edits to installed skill/plugin cache paths (~/.claude/skills/, ~/.claude/plugins/cache/, **/.bare/**) — always the repo worktree, verified by pwd.
6. Force-push only with --force-with-lease — never plain --force.
7. Commit before rebase — add → commit → fetch → rebase → push (a dirty tree aborts it).
8. No editorializing — state what changed, not how good it is (references/no-editorializing.md).