create-review-guide-skill — 2026-08-31

Built /create-review-guide (SSOT ~/ai-config/skills/create-review-guide/SKILL.md) — generates a zero-friction Review-<ProjectName>.md for a dev project: run commands, a check punch list, static-proof pointers, known gaps, test commands. GuideType: dev only, structured so a second type is an addition, not a rewrite. Registered in Core/AI/Skills/DASHBOARD.md, security-tested: 2026-08-31.

Retrofitted Review-LevPro.md (apps/sd-app/docs/) with the skill’s conventions — real test invocation, not just “looks right.”

Two real bugs found and fixed, both now baked into the skill’s guidance:

1. VS Code Markdown preview rejects the file: scheme. [label](file:///mnt/d/...) renders as literal unparsed text — confirmed via local markdown-it reproduction (validateLink returns false), not guessed. Fix: vscode://file/D:/... (VS Code’s own protocol handler) for any KB-vault-note link. Also: a link to a folder never opens in VS Code preview — link the individual files inside it, not the folder path. Both now documented at GlobalDevRules.md §3.11.
2. A Next Steps reply-placeholder regression, unrelated to the skill itself. A same-day fix (blank line before -) for a CommonMark setext-heading corruption bug traded one defect for another — Talbot flagged unwanted vertical space. The real fix was the marker, not the blank line: switched to * (asterisk is not a valid setext-underline character, so no blank line is needed at all). Landed in task-start.md/task-continue.md + SMTM_System.md.

Process failure worth flagging: claimed the blank line was removed in rounds 4, 5, and 6, while it was still physically present in the file each time — caught only when advisor() pointed straight at the agent’s own Read output. New AGENTS.md rule added: verify your own diff/output before claiming a fix landed, don’t trust the stated intent.

Commits: ai-config 9ae3db4, b809cdf, 8ad85ff, 2880aab, 1252617; monorepo 8c2bb66, 07940b1; KB vault 80d4971, 126a065.

LESSONS promoted: AGENTS.md (“claiming a fix landed ≠ verified”), GlobalDevRules.md §3.11 (VS Code Markdown link mechanics).

No successor — scope fully closed, confirmed live in Obsidian by Talbot.