Your development workflow is probably slower than it needs to be. Here's a setup that lets you ship features at breakneck speed while maintaining code quality.
The Stack
| Tool | Purpose |
|---|---|
| tmux + tmux-resurrect | Persistent terminal sessions that survive reboots |
| Git worktrees | Work on multiple branches simultaneously |
| Claude Code | AI pair programming in your terminal |
| GitSniper | Extract PR feedback into Claude Code instantly |
Let's break down each component.
1. tmux + tmux-resurrect for Persistence
Nothing kills momentum like losing your terminal state after a reboot. tmux keeps your sessions alive, and tmux-resurrect saves them across restarts.
Install
# Ubuntu/Debian
sudo apt install tmux
# macOS
brew install tmux
Install tmux-resurrect
git clone https://github.com/tmux-plugins/tmux-resurrect ~/.tmux/plugins/tmux-resurrect
Add to your ~/.tmux.conf:
# Enable mouse support
set -g mouse on
# Start windows and panes at 1, not 0
set -g base-index 1
setw -g pane-base-index 1
# tmux-resurrect
run-shell ~/.tmux/plugins/tmux-resurrect/resurrect.tmux
Key Bindings
| Keys | Action |
|---|---|
Ctrl+b then % |
Split pane vertically |
Ctrl+b then " |
Split pane horizontally |
Ctrl+b then arrow keys |
Switch between panes |
Ctrl+b then Ctrl+s |
Save session (resurrect) |
Ctrl+b then Ctrl+r |
Restore session (resurrect) |
Now your entire workspace persists across reboots. Each pane can serve as a dedicated workspace for a git worktree - switch between them with Ctrl+b and arrow keys.
2. Git Worktrees for Parallel Development
Git worktrees let you check out multiple branches simultaneously in separate directories. No more stashing, no more context switching pain.
The Setup
# You're on main, need to work on a feature
git worktree add ../myproject-feature-auth feature/auth
# Now you have:
# /code/myproject (main branch)
# /code/myproject-feature-auth (feature/auth branch)
Why This Matters
- Parallel work: Run tests on one branch while coding on another
- Quick hotfixes: Jump to a hotfix branch without disrupting your feature work
- Code review: Check out the PR branch in a separate worktree while keeping your work intact
Each worktree gets its own tmux pane with Claude Code running. Switch branches instantly without losing context.
3. Claude Code for AI Pair Programming
Claude Code is the CLI interface to Claude that understands your codebase. It can read files, run commands, and make changes - all from your terminal.
Install
npm install -g @anthropic-ai/claude-code
The Workflow
cd /code/myproject
claude
Claude Code indexes your codebase and becomes your pair programmer. Ask it to:
- Implement features based on specs
- Debug failing tests
- Refactor code
- Explain complex logic
After a reboot, restore your tmux session and resume your Claude Code conversation exactly where you left off:
claude --continue
This picks up the previous session context, so you don't lose your place.
4. GitSniper for Code Review → Claude Code
Here's the workflow bottleneck most people don't talk about: getting PR feedback into your AI assistant.
You open a PR, get 15 comments across 8 files. Now what? Manually copy each comment? Screenshot everything? Summarise it yourself?
GitSniper automates this.
Install
The Workflow
- Open your PR/MR in GitHub or GitLab
- Click the GitSniper button
- All comments are extracted with full context (diff snippets, line numbers, threading)
- Paste directly into Claude Code
> Here's the feedback from my PR review:
[paste GitSniper output]
> Please address each comment and explain your changes.
Claude Code now has the full context of every review comment, including the exact code being discussed. It can systematically work through each piece of feedback.
The Complete Workflow
Here's how it all comes together:
Morning Startup
tmux
# Press Ctrl+b then Ctrl+r to restore yesterday's session
Everything is exactly where you left it - worktrees, panes, even scroll position.
In each pane, resume your Claude Code session:
claude --continue
Feature Development
# Create a worktree for your new feature
git worktree add ../myproject-feature-x feature/x
# New tmux pane for this worktree (Ctrl+b then %)
cd ../myproject-feature-x
claude
> Implement user authentication using JWT tokens.
> Here's the spec: [paste spec]
Code Review Iteration
- Push your branch, open a PR
- Receive review comments
- Click GitSniper to extract all feedback
- Paste into Claude Code
> Here's the code review feedback:
[GitSniper output]
> Address each comment. For security concerns,
> explain why your approach is safe or implement the fix.
- Claude Code systematically addresses each comment
- Push, review cycle continues
Parallel Hotfix
# Urgent bug comes in - don't touch your feature branch
git worktree add ../myproject-hotfix-123 hotfix/critical-bug
# New pane (Ctrl+b then %)
cd ../myproject-hotfix-123
claude
> Critical bug: users can't log in.
> Error: "Token validation failed"
> Find and fix the issue.
Your feature work is untouched. Fix the bug, merge, delete the worktree, continue where you left off.
Quick Reference
Worktree Commands
git worktree add ../project-feature feature/x # Create
git worktree list # List all
git worktree remove ../project-feature # Remove
tmux Commands
tmux new -s myproject # New named session
tmux ls # List sessions
tmux attach -t myproject # Attach to session
Claude Code Commands
claude # Start new session
claude --continue # Resume previous session
Conclusion
This setup eliminates the friction points in modern development:
- tmux + resurrect: Never lose your workspace state
- Git worktrees: Work on multiple branches without context switching
- Claude Code: AI pair programming that understands your codebase
- GitSniper: Bridge between code review and AI assistance
The result: faster iteration cycles, better code quality, and fewer interruptions to your flow state.
Try it out. Your future self will thank you.