Manages git worktrees, base-ref resolution, branch syncing, cleanup, and recovery using native git commands.
npx skills add https://github.com/mimukit/skills --skill gitkit-mimukit
Please help me install this Agent Skill. Skill: gitkit Source: https://github.com/mimukit/skills/tree/main/skills/gitkit Command: npx skills add https://github.com/mimukit/skills --skill gitkit-mimukit
$WORKTREE_ROOT/<repo>/<branch>), enforcing one worktree per branch with idempotent, non-destructive teardown. - Base ref and sync: Resolve the true default branch through a five-step ladder, then sync feature branches with a rebase-first policy, one confirmation covering rebase plus --force-with-lease push, and unresolved review-thread counts disclosed up front. - Clean, rescue, and stack modes: Sweep merged worktrees and branches with squash-merge detection, recover lost commits from reflogs and ORIG_HEAD via additive branch restores, and manage stacked branches through the gh stack extension with plain-git degradation. - Use Case: A developer says "sync this branch with main" — the Skill fetches, rebases onto the resolved base, runs the repo's test gate, and force-pushes with a lease, reporting exactly what changed. ## Quick Start Ask the agent to spin up a worktree for issue 42 and sync my current branch with the base branch.High-intent search queries and answers about installing and using this skill.
Fetch origin first, then run git worktree add -b <branch> under $WORKTREE_ROOT/<repo>/<branch> from the resolved base ref. If a worktree already exists for that branch, adopt it and report the path instead of creating a second one.
Rebase onto the base by default, even for published branches, so the branch reads as a linear sequence of its own commits. Merging the base in is an exception requiring a stated reason, such as unresolved review threads that a force-push would mark outdated.
Query gh repo view --json defaultBranchRef first, then fall back to git symbolic-ref refs/remotes/origin/HEAD, repair it with git remote set-head origin --auto, check origin/main or origin/master, and ask the user only after all of those fail.
A squash merge writes one new commit with no parent link to the branch, so ancestry checks report it as unmerged. Detect it by comparing the branch's combined patch-id against commits on the base using git patch-id --stable.
Check git status for an in-progress rebase and abort it, then search the HEAD and branch reflogs, ORIG_HEAD, and the stash list. Restore by creating a new branch at the chosen SHA rather than moving any existing ref, and never run git gc or prune during recovery.
Yes, the topology is reproducible with plain git: create each layer with git switch -c from the parent branch and open pull requests targeting the parent with gh pr create --base. You lose the stack map, automatic restacking, and cascade merging.
NVIDIASummarize GitHub pull request diffs and identify key design decisions.
fallow-rsCommits, pushes, and opens a ready pull request for local changes on GitHub.
coco-researchRemove a GSD workspace and clean up associated git worktrees.
aarushlohitCreate and manage isolated Git worktree environments for feature branches.