ez

Agent-first version control. Stacked PRs, worktree isolation, zero friction.

---

ez makes version control invisible for AI coding agents. Four commands cover the entire development lifecycle. Multiple agents work on the same repo without stepping on each other.

Install

pip install ez-stack
ez setup --yes
ez init

The 4 Commands

ez create feat/auth              # Start: worktree + branch + cd
ez push -am "feat: add auth"     # Ship: stage + commit + push + PR
ez sync --autostash              # Sync: pull trunk, clean merged, restack
ez delete feat/auth --yes        # Done: remove worktree + branch

That's it. No git add, no git commit, no gh pr create, no cd.

Why ez?

For agents: Each ez create gives the agent an isolated worktree. Multiple agents work in parallel on the same repo without merge conflicts. Structured JSON output, mutation receipts, and exit codes let agents verify every operation.

For humans: Stacked PRs become effortless. Auto-restacking, auto-cleanup of merged branches, and a dashboard that shows everything at a glance.

Dashboard

ez list

     BRANCH                         PR       CI     AGE    PORT    STATUS
--------------------------------------------------------------------------------
     main (trunk)                   -        -      2m     -       -
  *  feat/auth                      #42      ✓      5m     14832   clean
     feat/api                       #43      ⏳     15m    11247   2M 1U
     feat/ui                        -        -      1h     16503   no worktree

Shows all branches with PR status, CI pass/fail, time since last commit, deterministic dev port per worktree, and working tree state. ez list --json for machine output.

Multi-Agent Workflow

# Agent 1 (terminal 1)
ez create feat/auth --from main
# ... works in .worktrees/feat-auth ...
ez push -am "feat: auth system"

# Agent 2 (terminal 2, same repo)
ez create feat/api --from main
# ... works in .worktrees/feat-api ...
ez push -am "feat: API routes"

# No conflicts. Each agent has its own worktree.

Stacked PRs

# Build a stack of dependent changes
ez create feat/auth-types
ez commit -m "add auth types"

ez create feat/auth-api          # stacks on auth-types
ez commit -m "add auth API"

ez submit                        # pushes all, creates PRs with correct bases

# After the first PR merges:
ez sync                          # cleans up, restacks remaining branches

Worktree Hooks

Create .ez/hooks/post-create/default.md to give agents setup instructions:

# Worktree Setup
1. `npm install`
2. `cp .env.example .env`
3. Start dev server on port $EZ_PORT

Hooks are markdown instructions, not scripts. ez prints them, the agent follows them. Use --hook <name> for project-specific hooks, or --hook alone to list available hooks.

All Commands

Flagship

Command	Description
ez create <name>	Create worktree + branch (default). --from main for independent work. --no-worktree for branch only.
ez list	Dashboard: branches, PRs, CI, age, ports, working tree state. --json for machine output.
ez delete [name]	Delete branch + worktree. Auto-detects worktrees. --yes for agents.
ez push	Push + create/update PR. -am "msg" to stage+commit+push in one step.

Committing

Command	Description
ez commit -m "msg"	Commit + restack children
ez commit -am "msg"	Stage tracked files + commit
ez commit -m "msg" -- path1 path2	Stage specific files + commit
ez commit --if-changed	No-op if nothing staged
ez amend	Amend last commit + restack

Syncing

Command	Description
ez sync	Fetch trunk, clean merged branches, restack
ez sync --autostash	Stash before sync, restore after
ez sync --dry-run	Preview what sync would do
ez restack	Rebase children onto current branch tip

Navigation

Command	Description
ez switch <name>	Switch to branch (cd's to worktree if applicable)
ez switch <pr-number>	Switch by PR number
ez up / ez down	Navigate the stack
ez top / ez bottom	Jump to stack endpoints

Inspection

Command	Description
ez log	Visual stack tree with PR status
ez log --json	Stack as JSON
ez status	Branch info + working tree state
ez status --json	Branch info as JSON
ez diff	Diff vs parent (what the PR reviewer sees)
ez diff --stat	Diffstat summary
ez diff --name-only	Changed file names
ez parent	Print parent branch name to stdout

PRs

Command	Description
ez submit	Push entire stack + create/update all PRs
ez pr-link	Print PR URL to stdout
ez pr-edit --title "..." --body "..."	Edit PR metadata
ez draft / ez ready	Toggle PR draft status
ez merge	Merge bottom PR via GitHub

Setup

Command	Description
ez setup --yes	Configure shell integration
ez skill install	Install the ez-workflow skill for AI agents
ez update	Update to latest version

Agent Integration

Install the skill so agents auto-discover ez:

ez skill install

This writes the ez-workflow skill to .claude/skills/ez-workflow/SKILL.md. Agents using Claude Code (or any tool that reads .claude/skills/) will automatically use ez for all git operations.

See SKILL.md for the full agent workflow, and reference.md for the complete command reference.

How It Works

• Worktrees give each agent an isolated copy of the repo with its own branch
• Stack metadata in .git/ez/stack.json tracks branch parents and PR numbers
• Auto-restacking via git rebase --onto keeps children up to date when parents change
• Mutation receipts (JSON on stderr) let agents verify every operation
• Progressive help — ez, ez <cmd>, ez <cmd> --help each give more detail

Prerequisites

• git 2.38+
• gh (GitHub CLI), authenticated via gh auth login
• Python 3.8+ (for pip install) or download binaries from Releases

License

MIT. See LICENSE for details.