// Update the warp-command-signatures dependency hash in warp to the latest commit from warpdotdev/command-signatures:main.
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.
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.
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 | update-command-spec-version |
| description | Update the warp-command-signatures dependency hash in warp to the latest commit from warpdotdev/command-signatures:main. |
This skill automates updating the warp-command-signatures git dependency in warpdotdev/warp to the latest commit on warpdotdev/command-signatures:main, then opens a PR with a summary of what changed.
All scripts live in this skill's scripts/ directory.
gh CLI authenticated with access to warpdotdev/warp and warpdotdev/command-signaturesssh://git@github.com/warpdotdev/...)list_merged_prs.py)cargo (for updating Cargo.lock)Run the scripts in order. The skill directory is wherever this SKILL.md lives; reference scripts relative to it.
bash <skill-dir>/scripts/ensure_repos.sh
This clones or fetches both ~/warp and ~/command-signatures.
OLD_HASH=$(bash <skill-dir>/scripts/get_current_hash.sh)
NEW_HASH=$(bash <skill-dir>/scripts/get_latest_hash.sh)
If OLD_HASH equals NEW_HASH, tell the user that command-signatures is already up to date and stop.
python3 <skill-dir>/scripts/list_merged_prs.py "$OLD_HASH" "$NEW_HASH"
This outputs JSON with four keys: prs (all PRs), new_completions, bug_fixes, and other. Each entry has number and title.
Review the categorization. The script uses simple heuristics (titles starting with "add" → new completion, titles containing "fix" or "bug" → bug fix). Move any miscategorized entries before composing the description.
bash <skill-dir>/scripts/update_and_branch.sh "$NEW_HASH"
This checks out a new branch completions-bot/update-command-signatures-<first 8 chars of NEW_HASH> from origin/master in ~/warp, updates the rev in Cargo.toml, and syncs Cargo.lock.
Write a PR description following this structure (match the warp PR template). Save it to a temp file, e.g. /tmp/completions_pr_body.md.
## Description
Updates `warp-command-signatures` to <NEW_HASH short>.
### Merged PRs
- <PR title> (warpdotdev/command-signatures#<number>)
- <PR title> (warpdotdev/command-signatures#<number>)
- ...
## Changelog Entries for Stable
CHANGELOG-IMPROVEMENT: <single line covering all new completions, subcommands, generators, and updates>
CHANGELOG-BUG-FIX: <single line covering all bug fixes>
Guidelines for changelog entries:
CHANGELOG-IMPROVEMENT line that summarizes all new completions and improvements. If there are many commands, use only their short names. For example: "Added completions for aws ec2, scp, claude, and docker-compose service names."CHANGELOG-BUG-FIX line that summarizes all bug fixes. For example: "Fixed npm install short-form command priority and HTML entity rendering in completion specs."bash <skill-dir>/scripts/submit_pr.sh "$NEW_HASH" <absolute_path_to_temp_description_file>
This commits the changes, pushes the branch, and opens a draft PR titled "[Completions] Bump command-signatures to <first 8 chars of NEW_HASH>" against master.