add skill for setting up local testing

Author: acarl005

.agents/skills/add-command-spec/SKILL.md

@@ -68,6 +68,8 @@ Format the JSON spec with `npm run format -- command-signatures/json/<command>.j
 
 Run `script/presubmit` to verify formatting, linting, and tests all pass (this runs `cargo fmt --check`, `cargo clippy`, and `cargo test`).
 
+To verify completions end-to-end in a real Warp session, use the **test-local-warp** skill, which covers building and running Warp against a local checkout of this repo. This requires computer use to be enabled since Warp is a GUI application.
+
 ## Reference Examples
 
 - **Simple spec with generator**: `json/kill.json` + `src/generators/kill.rs` — minimal example showing `generatorName` usage for process and signal completions

.agents/skills/test-local-warp/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: test-local-warp
+description: Test command-signatures changes locally by running Warp terminal against a local build of this crate. Use when the user wants to verify completion spec changes, generator changes, or other modifications in a real Warp session before merging.
+---
+
+# Testing command-signatures with a Local Warp Build
+
+## Overview
+
+`warp-command-signatures` is consumed by `warp-internal` as a git dependency. To test changes locally, temporarily point `warp-internal` at a local checkout of this repo, then build and run Warp.
+
+## Prerequisites
+
+- A local checkout of both `warp-internal` and `command-signatures`.
+- **Computer use must be enabled** — Warp is a GUI application, so verifying completions requires screen interaction.
+
+## Steps
+
+### 1. Patch the dependency in warp-internal
+
+In the `warp-internal` repo's root `Cargo.toml`, find the `warp-command-signatures` line under `[workspace.dependencies]`:
+
+```toml
+warp-command-signatures = { git = "ssh://git@github.com/warpdotdev/command-signatures.git", rev = "...", default-features = false }
+```
+
+Replace it with a local path. Adjust the relative path based on where the two repos are checked out:
+
+```toml
+warp-command-signatures = { path = "../command-signatures/command-signatures", default-features = false }
+```
+
+Note the nested `command-signatures/command-signatures` — the outer directory is the repo root (Cargo workspace), the inner one is the `warp-command-signatures` crate.
+
+### 2. Build and run Warp
+
+From the `warp-internal` repo:
+
+```sh
+cargo run --features fast_dev
+```
+
+### 3. Verify changes
+
+Open the locally-built Warp and test completions for the commands you modified. Type the command and trigger tab completion to confirm specs and generators behave as expected.
+
+### 4. Clean up
+
+Revert the `Cargo.toml` change in `warp-internal` before committing. The local path override should never be checked in.
+
+### 5. Release
+
+After your command-signatures PR is merged, update the `rev` in `warp-internal/Cargo.toml` to the new commit hash on `main` and open a PR in `warp-internal` to pick up the changes.