gt

Tool passed security scan

Malicious tool definition detected

Run sync gt sync # Output: # "Fetching latest from origin..." # "Rebasing stacks on latest main..." # "Found merged branches: phase-1" # "Delete phase-1? [y/n]" # 2. Confirm deletion y # Result: # - phase-1 deleted locally # - phase-2 rebased onto main (becomes bottom of stack) # - phase-3 rebased onto phase-2 # - phase-2 PR base updated to main on GitHub ``` ### Pattern 6: Splitting Large Changes **Goal**: Break up a large commit into reviewable pieces.

Tool: references/gt-reference.md [6/6] Description: ".graphite_cache_persist" if not cache_file.exists(): print("No Graphite cache found - run 'gt repo init'") return data = json.loads(cache_file.read_text()) print("Tracked branches:") for branch, meta in data.get("branches", {}).items(): parent = meta.get("parentBranchName", "none") print(f" {branch} -> {parent}") ``` ### Recovery from Corrupted State If Graphite metadata becomes corrupted: ```bash # Nuclear option: Re-initialize (loses stack r

Tool passed security scan

Malicious tool definition detected

# Modify (auto-restacks upstack branches) gt modify -m "Address review feedback" --no-interactive # Resubmit stack gt submit --stack --no-interactive ``` ### Pattern 3: Adding to Existing Stack Insert a new branch in the middle: ```bash # Checkout the parent where you want to insert gt checkout phase-1 --no-interactive # Create new branch with --insert gt create phase-1.5 --insert -m "Add validation" --no-interactive # Submit new PR gt submit --no-interactive ``` ### Pattern 4: Syncing After Mer