git-workflowlisted

Routes git workspace and branch-integration practices. Use when starting feature work that needs an isolated workspace or git worktree, before executing a risky implementation plan, when the current workspace has unrelated changes that should not mix with the task, or when implementation is complete and verification passes and the branch needs a structured integration decision: merge locally, push and create a PR, keep the branch, or discard the work.
danielleit241/forge · ★ 1 · AI & Automation · score 70

Install: claude install-skill danielleit241/forge

# Git Workflow Thin router over the two git workflow checklists. Each reference keeps the full original content of the former standalone skill. ## Route | Situation | Read | | --- | --- | | Need isolated workspace/worktree for feature work, risky plan, or dirty workspace | `references/worktrees.md` | | Implementation complete and verified; choose merge / PR / keep / discard | `references/finishing-branch.md` | ## Usage Notes - The two references cover opposite ends of the same lifecycle: isolate before starting, integrate after verifying. Load both when finishing work inside a worktree you created. - Never declare unverified work complete: `finishing-branch.md` starts from a passing check, and `worktrees.md` requires a baseline check after setup. - When a forge work item is active, `ship` owns the readiness verdict; `finishing-branch.md` covers only the integration mechanics after `READY`.