// Customize Warp keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the default for X").
Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channel_versions.json.
Repo-specific bug reproduction guidance for Warp. Specializes the core reproduce-bug-report skill for logged-out Warp UI repros, exact reporter-version installs, and login-free onboarding.
Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding branches proposed by those initial explorers. Use this whenever the user asks to test, document, screenshot, or walk through the Warp first-time install/onboarding experience in a cloud Linux environment.
Turn rough feedback about the Warp app into a filed GitHub issue or duplicate-issue response for `warpdotdev/warp`. Use ONLY when the user explicitly wants to report a problem with the Warp terminal/IDE/app itself—not when they're working on their own code, managing their own GitHub repos, or doing general software development tasks. SKIP when: the user is creating/managing GitHub issues or PRs for their own projects, reviewing PRs, diagnosing CI failures, using `gh` CLI for repo management, or performing any GitHub workflow not specifically about reporting a problem with the Warp application itself.
Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.
Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.
| name | change-keybinding |
| description | Customize Warp keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the default for X"). |
Use this skill when the user wants to remap, rebind, or remove a Warp keyboard shortcut.
User customizations live at:
{{keybindings_file_path}}
This is the exact path Warp reads at launch — it is platform- and channel-specific (e.g. under ~/.warp*/ on macOS, under XDG config dirs like ~/.config/warp-terminal/ on Linux, and under %LocalAppData% on Windows). Use this path verbatim — do not infer a different one from the user's home directory layout. Create the file (and any missing parent directories) if it does not exist.
A flat YAML map of action_name → key_trigger. Action names contain a colon, so they must be quoted:
"workspace:toggle_ai_assistant": ctrl-s
"editor_view:delete_all_left": cmd-shift-A
"workspace:toggle_command_palette": none
Triggers use Warp's normalized form — get this exactly right or the binding silently fails to load.
ctrl-alt-shift-cmd-meta-. Cross-platform alias: cmdorctrl- (becomes cmd on macOS, ctrl elsewhere).shift, the letter is lowercase (ctrl-s). With shift, the letter is uppercase (shift-A, never shift-a). Mixing them is invalid.space, enter, escape, tab, backspace, delete, insert, up, down, left, right, home, end, pageup, pagedown, f1–f20, numpadenter. Always lowercase, even with shift (ctrl-shift-space, shift-tab — never ctrl-shift-SPACE). Use the literal word space — not " ".cmd-=, cmd-,, cmdorctrl-/.none. The action becomes unbound.Translate user phrasing into this form: Ctrl+S → ctrl-s, Cmd+Shift+P → cmd-shift-P, Ctrl+Space → ctrl-space.
Defaults are compiled into Warp and are not discoverable from the keybindings file on disk. There is no catalog the agent can consult to map a description or current shortcut to an action name. Pick the right strategy based on how the user described the change:
By action name ("set workspace:toggle_command_palette to cmd-p"): the user already gave you the name — write it directly.
By description or current key combo ("rebind the command palette to cmd-p", "change ctrl+space to ctrl+s"): you don't have the action name and cannot reliably guess it. Do not invent one. Direct the user to the keybindings editor (workspace:show_keybinding_settings, default cmd-ctrl-k on macOS; Settings → Keyboard Shortcuts on other platforms) — they can search by description or current shortcut there and either edit the binding in place or share the canonical namespace:action_name so you can write it.
{{keybindings_file_path}} if present. Preserve every existing entry — only add or update the one you're changing.settings.toml which hot-reloads. They can quit with cmd-Q (macOS) or the equivalent on their platform and reopen Warp.Remap an existing custom binding by old trigger:
# before
"workspace:toggle_ai_assistant": ctrl-space
# after
"workspace:toggle_ai_assistant": ctrl-s
Remove a default shortcut:
"workspace:toggle_keybindings_page": none
Shift combined with a special key (note the special key stays lowercase):
"workspace:toggle_ai_assistant": ctrl-shift-space
Cross-platform binding using the cmdorctrl- alias (resolves to cmd on macOS, ctrl elsewhere):
"workspace:toggle_command_palette": cmdorctrl-shift-P