// 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.
Orchestrate and verify command-spec Oz runs for Linear tickets. Starts an implementation run using the add-command-spec skill, verifies all edited/created generators have meaningful screenshots, and retries with follow-up runs until validation passes. Use this skill whenever you need to implement and fully validate a command-spec Linear ticket end-to-end, or when a user provides a Linear ticket that involves adding or modifying command completions in the command-signatures repo.
Update the warp-command-signatures dependency hash in warp to the latest commit from warpdotdev/command-signatures:main.
Guide for adding new command completion specs to warp-command-signatures. Use when creating a new JSON spec for shell command completions, adding generators for dynamic suggestions, or extending existing command specs.
| 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. |
warp-command-signatures is consumed by the warp app as a git dependency. To test changes locally, temporarily point warp at a local checkout of this repo, then build and run Warp.
warp and command-signatures.In the warp repo's root Cargo.toml, find the warp-command-signatures line under [workspace.dependencies]:
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:
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.
From the warp repo:
cargo run --features fast_dev
Open the locally-built Warp and test completions for the commands you modified. Type the command and use the Tab key to trigger the completion menu to confirm specs and generators behave as expected.
Note: The completions menu does not work with equal-sign-delimited options (e.g.
--foo=bar). Always use space-delimited syntax when testing (e.g.--foo bar).
Revert the Cargo.toml change in warp before committing. The local path override should never be checked in.