cli-tmux
Use tmux to run and test our interactive CLI/TUI end-to-end. Includes how to start, send keys, capture output, and cleanly stop (double Ctrl+C).
What this skill does
# cli-tmux skill: run & test the CLI using tmux ## Use this skill when - The user asks to test the CLI end-to-end and it is interactive (TUI prompts, key navigation). - A command needs a real TTY or long-running process (dev server) that should keep running while we do other tasks. ## Golden rules 1. **Prefer `scripts/tmuxctl.sh` over raw tmux commands** for repeatability. 2. Use an **isolated tmux server socket** so we don't interfere with the user's real tmux sessions. 3. Use a predictable session name: `agent-cli`. 4. Always capture pane output after each interaction and summarize it before proceeding. 5. Always clean up: stop the TUI and kill the session at the end (unless the user wants it left running). ## tmuxctl.sh wrapper (preferred) Prefer `scripts/tmuxctl.sh` over raw tmux commands for repeatability: - `scripts/tmuxctl.sh start` - Create new tmux session - `scripts/tmuxctl.sh run ./bin/ourcli` - Run command in the session - `scripts/tmuxctl.sh keys Down Down C-m` - Send keystrokes - `scripts/tmuxctl.sh capture` - Capture pane output - `scripts/tmuxctl.sh stop` - Stop the TUI (double Ctrl+C) - `scripts/tmuxctl.sh kill` - Kill the session ## Our CLI/TUI specifics - To exit the TUI, send **double Ctrl+C**: `C-c` then `C-c`. - If double Ctrl+C doesn't exit, fallback to killing the tmux pane/session. ## Standard tmux setup (isolated socket) - Socket path: `.tmp/tmux-agent.sock` - Session: `agent-cli` - Pane target: `agent-cli:0.0` ### Create session (if missing) - Ensure `.tmp/` exists. - Start detached session in repo root: - `tmux -S .tmp/tmux-agent.sock new-session -d -s agent-cli -c "$PWD"` ### Start the CLI - Send the run command (replace with our real command): - Example: `./bin/ourcli` OR `pnpm ourcli` OR `go run ./cmd/ourcli` - Use: - `tmux -S .tmp/tmux-agent.sock send-keys -t agent-cli:0.0 "<COMMAND HERE>" C-m` ### Interact - Send keys as needed: - Enter: `C-m` - Up/Down: `Up` / `Down` - Quit: `C-c C-c` (double) ### Capture output (after each step) - `tmux -S .tmp/tmux-agent.sock capture-pane -t agent-cli:0.0 -p` ## End-to-end CLI test recipe 1. Start session (or reuse if running). 2. Launch CLI command. 3. Capture initial screen and confirm expected prompt/state. 4. Perform the requested flows (send keys + capture after each step). 5. Exit TUI with `C-c C-c`, capture output to confirm exit. 6. Kill session (unless user asked to keep it). ## Cleanup - Preferred: - Send `C-c C-c`, then `tmux ... kill-session -t agent-cli` - If tmux is wedged: - `tmux -S .tmp/tmux-agent.sock kill-server`
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.