vkb

Use this skill only when the user explicitly asks to use `vkb`. Do not invoke it automatically or as a fallback during other tasks. Use the session's `vkb` command for code structure and saved design context: ```sh vkb explore "how session creation works" vkb search "symbol or topic" vkb node "symbol-id-from-search" vkb callers "symbol-id" 2 vkb callees "symbol-id" 2 vkb impact "symbol-id" 3 vkb path "from-symbol-id" "to-symbol-id" vkb files "src/session" vkb memories "topic" vkb memory "entry-id-from-results" vkb notes "topic" vkb note "vault-id-from-results" "relative/path.md" vkb status ``` Start with `explore` for architecture questions and flows: it calls the pinned upstream `codegraph_explore` handler and returns its source and relationship context. Use `search` to obtain exact IDs before `node`, `callers`, `callees`, `impact` or `path`. Search accepts upstream field filters such as `kind:function`, `lang:rust` and `path:src/session`. Its result reports `hasMore` rather than claiming an exact total from a ranked search. `path` follows directed call edges; no result means no indexed path, not proof that no runtime flow exists. Traversal depth defaults to 3 and is bounded by the backend; truncated results include full counts. Code queries resolve the command's current checkout, including Git worktrees, and synchronize its enabled index before reading. `search` returns code symbols and knowledge entry summaries separately; `node` returns source, incoming/outgoing relat...