Lattice

Stack your prs and make yourself and your reviewers happy

Lattice (lt) is my take on implementing a stacked branch workflow on top of git and a git forge like github.

It's based heavily on graphite, which I think has an excellent "mental model" for stacking. If you're not familiar, the basic idea is to treat big features (or features that depend on each other) as separate branches, and think of your "overall PR" as being made up of the composition of all of those smaller branches.

Why Lattice?

Basically because stacking is great, and graphite is great, but the model where there's ANOTHER saas where I'm doing PR reviews (aside from github) never really clocked for me.
I've also tried a couple of other tools, like git spr or git town, but they just don't click for me.

So, I got a bunch of agents to build lattice for me. Almost 100% of this codebase has been generated by a combination of gpt pro, codex, and opus. I've specified the architecture and overall feature set, along with test strategies and acceptance criteria.

I'm using this day-to-day, and I love it. YMMV.

Lattice gives you:

• Stacked branches synchronized with github PRs
• A single Rust binary (lt) with zero runtime dependencies
• All your code review stays in GitHub
• Metadata stored in Git itself (portable, inspectable, no external DB)

Quick Start

# Install from crates.io
cargo install latticework

# Or build from source
cargo install --path .

# Initialize in your repo
lt init

# Authenticate with GitHub
lt auth

# Start stacking
lt create feature-auth      # Create a branch
# ... make changes, commit ...
lt create feature-ui        # Stack another branch on top
# ... make changes, commit ...
lt submit --stack           # Push and create PRs for the whole stack

Your PRs will automatically include a stack visualization:

Commands

Daily Workflow

Navigation

Stack Management

GitHub Integration

Maintenance

Setup

Unique Features

Self-Healing with doctor

Made changes outside of Lattice? Ran a manual git rebase? The doctor command detects inconsistencies and offers explicit repair options:

lt doctor
# Detected: Branch 'feature-x' base commit is not reachable from parent
# 
# Repair options:
#   [1] Restack 'feature-x' onto 'main'
#   [2] Update metadata to match current state
#   [3] Untrack 'feature-x'

Doctor never guesses. It shows you what's wrong and lets you choose how to fix it.

Stack Comments in PRs

When you submit PRs, Lattice automatically adds a stack visualization to each PR description:

### Stack

| | Branch | PR |
|---|--------|-----|
| ⬆️ | `feature-auth` | #10 |
| 👉 | `feature-ui` | #11 |
| ⬇️ | `feature-tests` | #12 |

Reviewers instantly see where each PR fits in the larger change. The table updates automatically when you re-submit.

Freeze Protection

Working with a teammate's branch? Freeze it to prevent accidental modifications:

lt get 123                  # Fetch PR #123 (frozen by default)
lt freeze feature-shared    # Or freeze any branch explicitly

Frozen branches block rebases, amends, and other rewrites until you explicitly unfreeze them.

Empty Branch Support

Plan your stack before writing code:

lt create step-1    # No commits yet, just a placeholder
lt create step-2    # Stack another placeholder
lt create step-3    # And another
lt down 2           # Go back to step-1 and start coding

Configuration

Lattice uses a layered configuration system:

1. CLI flags (highest priority)
2. Repo config (.git/lattice/repo.toml)
3. Global config (~/.lattice/config.toml)

Common settings:

lt config set trunk main              # Set default trunk branch
lt config set submit.draft true       # Create PRs as drafts by default
lt config list                        # See all settings

Global Flags

These flags work with any command:

Also notable

• Graphite
• Git town
• Git spr

Contributions

Have a feature you want to see or implement? Please do! Open PRs to your hearts content.

License

MIT