chhoumann

Verify an Obsidian plugin change/fix actually works by driving the REAL Obsidian app in a dev vault via the `obsidian` CLI (eval / dev:console / dev:errors / dev:screenshot / command / plugin:reload) and asserting on persisted state — instead of trusting unit tests with mocks (jsdom can't load real Obsidian). Use when asked to verify/QA a fix, confirm a feature works end-to-end, check that something persists, reproduce a user-reported bug in the real app, or validate before merging — especially stateful UI (settings, modals, drag-reorder, lists). FIRST read the repo's AGENTS.md/CLAUDE.md for the vault name, plugin id, dev commands, and any QA matrix.

Install or update the Codex Atuin PreToolUse/PostToolUse hook in the current workspace or user config, then validate it by checking Atuin history.