What problem does it solve? Monaco built-in commands often cannot be found in the project's command palette or Keyboard Shortcuts editor, and some cannot be rebound even though they work from the right-click menu or default keys. This Skill diagnoses which Monaco registration mechanism a command uses and wires it into the project's CommandsRegistry and KeybindingsRegistry correctly. ## Core Features & Use Cases - Mechanism Detection: Distinguishes registerEditorAction commands from registerAction2 commands using runtime checks and source inspection, since each requires a different integration path. - Three Integration Paths: Covers auto-bridged EditorActions, explicit Action2 wrappers using getAction().run(), and action2 wrappers using editor.focus() plus editor.trigger(). - Double-Trigger Prevention: Removes Monaco's own default keybindings via addKeybindingRule when a project-level default key is declared, with a single exported id list as the source of truth. - Use Case: When Go to Definition works via F12 but cannot be found in the command palette or rebound in the Keyboard Shortcuts editor, use this Skill to wrap it as a project Action2 with VSCode-aligned id and default key, plus tests. ## Quick Start Ask the AI to make a specific Monaco command searchable in the command palette and rebindable in the Keyboard Shortcuts editor.
