Agent skill · writing content · davila7
worktree-guide
Interactive guide for parallel development with Ghostty, git worktrees, and Lazygit. Use when setting up multi-task workflows or learning the worktree system.
Why this skill is useful
Provides a structured guide for using git worktrees and Ghostty, which includes specific commands and workflows that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Guide the user through parallel development workflows using Ghostty terminal panels, git worktrees, and Lazygit. This is both a teaching experience and a practical reference. --- Preflight Before starting, detect the user's environment: If not a git repo: This isn't a git repository. Navigate to a git project first, then come back to /worktree-guide. Check if we're in a worktree or main repo: Note the context for later guidance. --- Phase 1: Welcome & Context Detection Display based on environment: If in main repo: Use AskUserQuestion: "Learn the full workflow" — Start from Phase 2 "Just show keybindings" — Jump to Quick Reference "Create worktrees now" — Suggest /worktree-init "Something else" — Ask what they need If already in a worktree: Then run the equivalent of /worktree-check and provide contextual guidance. --- Phase 2: Ghostty Essentials EXPLAIN: SHOW: PAUSE - "Ready to learn about Lazygit? (Or skip to workflow)" --- Phase 3: Lazygit Essentials EXPLAIN: SHOW: PAUSE - "Ready for the full workflow walkthrough?" --- Phase 4: Complete Workflow (Guided) EXPLAIN: Step 4.1: Create Worktrees EXPLAIN: DO: Show example command: Step 4.2: Open Ghostty Panels EXPLAIN: DO: Step 4.3: Work in Each Panel EXPLAIN: Step 4.4: Deliver Completed Work EXPLAIN: Step 4.5: Clean Up EXPLAIN: --- Phase 5: Troubleshooting SHOW: --- Phase 6: Quick Reference Card SHOW: --- Guardrails Never execute destructive commands without confirmation (worktree remove, branch delete) Always verify location before suggesting worktree operations If user seems lost, offer /worktree-check first Never force-delete branches that aren't merged Don't assume tools are installed — check for lazygit availability if suggesting it Respect user's pace — don't rush through sections if they want to practice Keep the reference card available — offer to show it whenever relevant
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/worktree-guide