Files
command-center/agent/managed-skills/key-chord-source-audit/SKILL.md
T

2.3 KiB

name, description
name description
key-chord-source-audit Answer "what does chord X do" on Dank workstations: identify which layer (omp TUI, browser tool, niri, terminal) owns the chord before answering

Key-chord source audit

Frank asks "what does mod+r / ctrl+X do?" — the chord lives in ONE layer of the stack; answering from the wrong layer is wrong. Check layers in order, in ONE pass.

Layers, in Frank's stack (most of his "mod" questions are niri)

  1. niri compositor (Mod = Super). Keybinds are NOT in ~/.config/niri/config.kdl — it only includes cfg/*.kdl. Grep ~/.config/niri/cfg/keybinds.kdl directly. Notation: Mod+R, Mod+CTRL+Alt+H. Preset-width cycle (Mod+R) uses preset-column-widths from cfg/rules.kdl; no rule → built-in proportions 3/4, 1/3, 1/2, 2/3, 9/10, 1.
  2. omp TUI: defaults in ~/.bun/install/global/node_modules/@oh-my-pi/pi-coding-agent/dist/cli.js — grep defaultKeys:\["…" (array form) and defaultKeys:"…" (string form; needs a second pattern). Recognized modifiers: ctrl/shift/alt/super only; no meta/mod alias. User remaps: ~/.omp/agent/keybindings.yml (check existence first; absent = no remaps). Docs: omp://keybindings.md.
  3. omp browser tool: Mod+Key is Playwright notation (Mod → Ctrl on Linux, Cmd on macOS), used by tab.press(); e.g. Mod+R = page reload. Tern backend ternKey() throws on literal Mod; puppeteer path passes names through.
  4. Terminals/tmux: ~/.config/ghostty/config.ghostty + ghostty/auto/, foot.ini, kitty.conf, ~/.tmux.conf — keybind/bind/map lines.

Procedure

  1. Classify the notation the user used: Mod+… → niri/Playwright; Ctrl+… → TUI/terminal; tmux prefix → tmux.
  2. Grep that layer's config FIRST, expanding includes (config.kdl → cfg/*.kdl is the trap that caused a wrong answer).
  3. For omp bundle greps: two defaultKeys forms exist; super+r pattern also matches super+right — anchor with word boundary.
  4. Quote the exact config line as evidence; state the layer that owns the chord.

Verification

  • niri keybinds: grep -n "Mod+R" ~/.config/niri/cfg/keybinds.kdl (not config.kdl).
  • omp: grep -o '"app[^"]*":{defaultKeys:[^}]*' cli.js for app actions; grep -rn "defaultKeys" pi-tui/src/keybindings.ts for editor actions.