obsidian-test-vault-smoke

What problem does it solve?

After making changes to the personal-assistant Obsidian plugin (such as UI updates, Pagelet feature work, Chat or Memory modifications, or packaging changes), standard unit tests and build checks cannot catch regressions that only appear when running inside the actual Obsidian app. This Skill eliminates that gap by providing structured, tiered end-to-end validation workflows for the repo-local test vault.

Core Features & Use Cases

• Tiered Smoke Testing: Choose the lightest appropriate test tier (quick, app-runtime, full-ui, release-gate) based on the scope of your changes, avoiding wasted effort on overkill checks for small code updates.
• Obsidian CLI Integration: Run fast runtime validation, DOM state checks, console error capture, and screenshot evidence collection directly via Obsidian's CLI, no manual navigation required.
• Full UI/UX Validation: Verify visible layout, copy, accessibility, and user workflows (Pagelet review, Chat interaction, Memory prompts, settings) using Computer Use or direct app inspection for release confidence.
• Use Case: After updating the Pagelet review workflow or fixing a Chat layout bug, run the full-ui smoke tier to confirm the change works as expected for real users before merging or releasing.

Quick Start

Use the obsidian-test-vault-smoke skill to run end-to-end validation of the personal-assistant plugin in the repo-local test vault after UI, runtime, or Pagelet changes.