obsidian-qa

Run the full Obsidian CLI QA harness. Tests run directly against the registered test vault so the Obsidian CLI can operate against it. Results are snapshotted into a timestamped report dir at the end, then the fixture is restored via git.

Run only after the latest skill version is installed.

---

Setup

TIMESTAMP=$(date +%Y-%m-%d-%H%M)
REPORT_DIR="$(pwd)/qa/reports/qa-$TIMESTAMP"
mkdir -p "$REPORT_DIR"
VAULT_PATH="$(pwd)/qa/fixtures/test_vault"
CONFIG_PATH="$(pwd)/qa/fixtures/config.yaml"
SKILL_VERSION=$(grep '"version"' ~/.claude/plugins/marketplaces/obsidian-cli-skill/plugins/obsidian-cli/.claude-plugin/plugin.json 2>/dev/null | head -1 | grep -o '"[^"]*"' | tail -1 | tr -d '"' || echo "unknown")

Copy the example config and set vault_path to the test vault:

cp plugins/obsidian-cli/config.yaml.example "$CONFIG_PATH"
# Set vault_path to VAULT_PATH in config.yaml

The fixture vault at qa/fixtures/test_vault is registered with Obsidian, so CLI commands will actually persist to disk. All tests modify this vault directly. After the run, the fixture is restored.

---

Phase 1 — Parallel Tests

Launch all of the following in parallel using the Task tool with general-purpose subagents. Each subagent invokes the obsidian-cli skill, auto-approves any proposals, and returns a completion marker with a brief summary.

These tests touch different parts of the vault and can safely run at the same time.

T1 — Enrich Inbox

Invoke the obsidian-cli skill:

"Set frontmatter on everything in my Inbox folder — assign type and topic based on each note's content. My config is at <CONFIG_PATH>"

Auto-approve the proposal. If any CLI command fails, do not write files directly — report the exact CLI error and return [T1_FAIL]. Return [T1_COMPLETE] only if all changes were applied via the Obsidian CLI, with each file and the type/topic assigned.

T2 — Create Daily Template

Invoke the obsidian-cli skill:

"Create a daily note template with date, tags, and a section for notes of the day. My vault is at <VAULT_PATH>"