Testing & QA · Obsidian · For developers

Skill for testing Obsidian plugin features in this repository.

polyipseity/obsidian-terminal

A skill your agent uses when reviewing PRs, code changes, or conducting code audits in obsidian-terminal.

polyipseity/obsidian-terminal

Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format.

RafaelGB/Obsidian-ZettelFlow

A skill your agent uses when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.

thoreinstein/gemini-obsidian

Verify a Nexus change — pick a Jest lane, write a test that can actually fail, run the in-app Obsidian CLI loop, drive the eval harness, or fix a shipped-docs drift failure.

ProfSynapse/nexus

The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable.

RafaelGB/Obsidian-ZettelFlow

Stage 4 of the SDD pipeline — execute a ZettelFlow task checklist (in a GitHub issue comment) test-first (red → green → refactor), one commit per advance, keeping npm run verify green and CI green…

RafaelGB/Obsidian-ZettelFlow

Stage 2 of the SDD pipeline — turn a ZettelFlow spec (in the GitHub issue body) into a technical plan posted as an issue comment (approach, files by layer, Obsidian score-rule impact, test strategy…

RafaelGB/Obsidian-ZettelFlow

Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment.

RafaelGB/Obsidian-ZettelFlow

First-run walkthrough for Conducty. An agent skill from robertbarclayy/conducty.

robertbarclayy/conducty

Collect Obsidian plugin debug evidence for support and troubleshooting.

jeremylongshore/tons-of-skills-marketplace

Set up a fast Obsidian plugin development loop with hot reload.

jeremylongshore/tons-of-skills-marketplace