TUI Code Review

Arguments

• --parallel: Spawn specialized subagents per technology area
• Path: Target directory (default: current working directory)

Gates (sequence)

Advance only when each pass condition is true (reduces scope drift and unsubstantiated blocking claims):

Do not start Step 5 until G2 passes. Do not publish Critical/Major until G3 and G4 pass.

Step 1: Identify Changed Files

git diff --name-only $(git merge-base HEAD main)..HEAD | grep -E '\.go$'

Step 2: Detect Technologies

# Detect BubbleTea (required for TUI review)
grep -r "charmbracelet/bubbletea" --include="*.go" -l | head -3

# Detect Lipgloss styling
grep -r "charmbracelet/lipgloss\|lipgloss\.Style" --include="*.go" -l | head -3

# Detect Bubbles components
grep -r "charmbracelet/bubbles\|list\.Model\|textinput\.Model\|viewport\.Model" --include="*.go" -l | head -3

# Detect Wish SSH server
grep -r "charmbracelet/wish\|ssh\.Session" --include="*.go" -l | head -3

# Check for test files
git diff --name-only $(git merge-base HEAD main)..HEAD | grep -E '_test\.go$'

Step 3: Load Verification Protocol

Load beagle-go:review-verification-protocol skill and keep its checklist in mind throughout the review.

Step 4: Load Skills

Use the Skill tool to load each applicable skill (e.g., Skill(skill: "beagle-go:go-code-review")).

Always load:

• beagle-go:go-code-review
• beagle-go:bubbletea-code-review

Conditionally load based on detection:

Step 5: Review Focus Areas

Model/Update/View (Elm Architecture)

• Model is immutable (Update returns new model)
• Init returns proper initial command
• Update handles all message types
• View is pure function (no side effects)
• tea.Quit used correctly for exit

Lipgloss Styling