uhop

Walk the typed-edge neighborhood around a vault note. Backed by `GET /sections/{record_id}/neighborhood`. Use when the user says /vault-graph, asks "what does this note connect to and how", wants to see the wiki-link / classified-edge structure around a record, or needs to expand context beyond a single note. Returns layered records + typed edges; depth caps at 5. Requires vault-storage (`:8123`).

Find records semantically similar to a given vault note via embedding nearest-neighbours. Backed by `GET /sections/{record_id}/similar`. Use when the user says /vault-similar, asks "what other notes are like this one", or wants to discover related concepts beyond what's explicitly wikilinked. Returns ranked records by cosine similarity. Requires vault-storage (`:8123`) — Obsidian's REST API doesn't expose embeddings.

Read and write to the Obsidian knowledge base vault. Use when the user says /vault, asks to remember/save knowledge, wants to recall/query stored knowledge, asks to extract learnings from a project, or wants to log a session. Also use proactively at session end to capture non-obvious learnings.

Search the vault for notes matching a query. Backed by `POST /search/simple/` — works against both the Obsidian Local REST API (lexical only) and vault-storage (lexical + semantic). Use when the user says /vault-search, asks to find notes matching a phrase, or wants to locate the right note to read before answering a question. Returns ranked hits with snippets.

Detect drift between a project's current state (git + npm) and the baseline recorded in the vault's `projects/<name>/state.md`. Flags: new commits / tags / publishes since the baseline, local branch ahead/behind upstream, working-tree mods / stash entries / untracked files, git-tag ↔ npm-version mismatches. Used automatically by `/vault resume` and standalone via `/vault check`.

Propose missing `related:` entries for vault notes by reviewing BGE-retrieval candidates. Use when the user says /vault propose-related, asks to densify cross-references in the vault, or wants to expand `related:` arrays without reading every note manually. Loads top-N nearest neighbours per source note (excluding existing related: and body wikilinks), reasons about which are genuine semantic matches, writes accepted proposals to a review note in the vault.

Use the deep6 library for deep equality, deep cloning, unification, and pattern matching with logical variables in a JavaScript/TypeScript project. Use when adding structural comparison, structured clone with circular references, extensible pattern matching with extraction, or unification-based logic to a project that depends on `deep6`.

Write or update tests for a module or feature. Use when asked to write tests, add test coverage, or verify functionality for deep6.

Add support for a new type to unify and clone registries. Use when asked to support a new JavaScript type or custom class in deep6.

Add a new unifier module to deep6. Use when asked to create custom pattern matching logic or extend unification behavior.

Debug unification failures in deep6. Use when unification returns null or produces unexpected results.

Write or update tests using the tape-six testing library. Use when asked to write tests, add test coverage, or create test files for a project that uses tape-six.

Run tape-six's own test suite in this repo. Use when invoking tests, picking between Node/Bun/Deno or parallel/sequential variants, or debugging a failing run.

Set up `npm test` and run tape-six tests for a project. Use when configuring a project's test scripts in package.json, picking a runner, or debugging test invocation.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create test files in this repo.

Write a benchmark file for nano-bench (comparing multiple functions). Use when asked to create a benchmark, compare implementations, or measure performance of code variants.

Write a benchmark file for nano-watch (continuous single-function monitoring). Use when asked to create a watch benchmark, monitor performance over time, or check for memory leaks.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create test files.

Use the yopl Prolog-style logic engine in a JavaScript/TypeScript project. Use when adding rule-based search, pattern matching with extraction, constraint solving, type inference, planning, or expert-system style logic to a project that depends on `yopl`.

Debug solver failures or unexpected results in yopl. Use when `solve` produces no solutions, the wrong solutions, or unexpected variable bindings.

Write or update tests for a module or feature in yopl. Use when asked to write tests, add coverage, or verify functionality.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create typing tests for node-re2.

Review and improve English in documentation files for brevity and clarity. Use when asked to review docs, improve documentation writing, or edit prose for clarity.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create typing tests for stream-chain.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create new test files for stream-csv-as-json.

Write or update tape-six tests for a module or feature. Use when asked to write tests, add test coverage, or create test files.

Write or update tests using tape-six. Use when asked to write tests, add test coverage, or create test files.

Write or update dollar-shell tests for a module or feature. Use when asked to write tests, add test coverage, or create test files.