dsh-obsidian-plugin

Building an Obsidian plugin touches a surprisingly long chain of steps—scaffolding, bundling, format validation, vault deployment, sandboxed end-to-end testing, live inspection—each with its own pitfalls. dsh-obsidian-plugin collapses that chain into a single toolset a DSH agent can invoke end-to-end, so a natural-language request like "create an Obsidian plugin that …" triggers scaffolding, building, testing, deploying, and verification without the developer stitching steps together by hand.

The heart of the plugin is a four-tier verification pipeline. L1 performs static artifact, module-format, and manifest checks inside the build step. L2 loads the bundled file in plain Node against a stubbed Obsidian API, exercising the real Plugin lifecycle with no Obsidian installation required. L3 acts on your running app: read-only inspection, hot reload, and an approval-gated escape hatch that executes JavaScript inside the live instance. L4 launches a fully isolated Obsidian process (separate config directory, vault copy) and drives it with WebdriverIO for true end-to-end coverage, never stealing your focus or mutating your real vault. On top of that, official ESLint plugin linting, manifest/package.json version syncing, and intelligent build-tier resolution (honouring the project's own bundler config first, then falling back to local esbuild, then an actionable refusal) keep the loop tight and reproducible.

Ideal for developers who run DeepSeek Harness as their agent framework and want to iterate on Obsidian plugins with minimal ceremony. You no longer need to memorise esbuild entry-point priority rules, hand-edit community-plugins.json, or worry about accidentally flipping restricted-mode on a production vault. The tools resolve build configuration automatically, restrict writes to session-created test vaults, and—critically—always report what was verified and what was not, so a passing build never masquerades as a working plugin.