gji new feature/payment-refactorStart a task in its own worktree and land in the new directory immediately.
Git worktree CLI
Git worktrees without the hassle
gji creates separate worktrees for feature work, pull request review, experiments, and cleanup.
It adds navigation, shell handoff, predictable paths, and commands for creating, opening, syncing, and removing worktrees.
- Create branches and worktrees together with `gji new`
- Review pull requests without mutating your current checkout
- Jump between tasks with `go`, `back`, `open`, and `warp`
Typical session
Move between active tasks without reusing one checkout
Use one command set for creating worktrees, reviewing PRs, reopening existing tasks, and switching repos when needed.
gji pr 1234Open a pull request in isolation instead of mutating the checkout you were already using.
gji warp api/mainWhen several repos are active, jump straight to the matching worktree by repo and branch.
Default path layout
../worktrees/<repo>/<branch>Feature work in isolation
Open a clean worktree without disturbing the branch, install state, or shell you already have open.
PR review in isolation
Fetch review work into its own directory instead of turning your main checkout into a temporary review branch.
Fast navigation
Use go, back, open, and warp to move between active tasks without path hunting or stash churn.
What changes
Stop mutating one checkout for every task
Without gji
Stash changes, checkout another branch, reinstall dependencies, do the work, then switch everything back.
With gji
Open each task in its own worktree and switch directly between feature work, PR review, cleanup, and cross-repo tasks.
Core workflow
Commands for the work between commits
Open a new task cleanly
Create a branch and worktree together instead of reshaping one mutable checkout over and over.
Review and inspect in parallel
Use dedicated worktrees for pull requests, investigations, and experiments so each task keeps its own state.
Move without losing momentum
Use `go`, `back`, `open`, and `warp` to re-enter work quickly when several branches or repos are active at once.
Why teams keep it around
A better default for multi-branch work
Separate dependencies per branch
Each worktree keeps its own install state, build outputs, and editor context instead of sharing one unstable checkout.
Predictable paths and scriptable output
Use stable worktree locations, shell handoff, and JSON output to plug gji into scripts, editors, and agent workflows.
Navigation is broader than one command
Warp covers cross-repo jumps, but the day-to-day flow also includes new, pr, go, back, open, sync, and cleanup.
Documentation
Start with the parts you actually need
Installation
Install the CLI and wire shell handoff into zsh or bash.
Install gjiQuick Start
See the shortest path from feature work to PR review to cleanup.
Read quick startCommand Reference
Review `new`, `pr`, `go`, `warp`, `back`, `open`, and the rest of the day-to-day command surface.
Browse commands