branchName, validate, and create Git branches from the right base, following the repository's own naming convention, and choose or explain a branching strategy (GitHub flow, trunk-based, GitFlow). Use when asked to create or name a branch, check a branch name, rename or tidy branches, or decide where a br
commitWrite or create Git commits that follow the repository's message convention, including release-please and commitlint Conventional Commits. Use when asked to \"write a commit message\", \"write the commit message for the staged change\", \"commit the staged changes\", \"commit this\", split changes i
historyEdit and repair Git history safely without opening an editor, covering fixup commits with autosquash, rebase onto another base, cherry-pick backports, bisect to find a regression, and recovery of lost commits through the reflog. Use when asked to clean up or reorder commits, squash a branch, move a
worktreeManage Git worktrees directly with `git worktree` to create a checkout for a branch, list and inspect worktrees, lock or repair them, prune stale metadata, and remove finished ones without losing branches or local work. Use when the user asks to add, list, clean up, or fix git worktrees. Not for iso