Obsidian Plugin Review

This skill runs the local equivalent of the automated review on an Obsidian plugin. The output is in the same three-section format the developer dashboard shows, so you can catch issues before submitting a release.

The skill is a faithful mirror of the public parts of the reviewer: it uses the official eslint-plugin-obsidianmd and @typescript-eslint rulesets, plus a custom static-analysis scan for the ## Behavior capabilities (fs, child_process, clipboard, Vault API), plus a check for GitHub artifact attestations on the latest release. A small set of ## Releases / ## Source code rules are local-only (see references/rule-catalog.md for the full list and provenance).

When to use

• Before tagging a release, to catch issues that would fail the dashboard review.
• After a refactor, to confirm no new findings slipped in.
• When triaging findings from the dashboard log (paste a .log next to a local report and diff).
• When a plugin author wants a "what would the reviewer say?" preview without submitting.

When not to use

• For runtime behaviour tests — use the plugin's own test suite (e.g. vitest).
• For TypeScript compilation errors — use tsc --noEmit.
• For the actual submission — use the developer dashboard at https://community.obsidian.md/.