/check
Pre-publish checklist for a StackBrief article. Scans for unresolved placeholders, missing tool JSONs, stale lastVerified, and niche compliance. Returns CLEAR TO PUBLISH or BLOCKED.
Usage
/check [slug]
Where <slug> matches an article at content/articles/<slug>.mdx.
What it checks
| Check | Blocking |
|---|---|
| No [affiliate link] placeholders | Yes |
| No [NEEDS FACT CHECK: ...] strings | Yes |
| No {/* UNVERIFIED: ... */} comments | Yes |
| lastVerified is set and within 7 days | Yes |
| All tool slugs have matching JSON files | Yes |
| image field points to an existing file | Yes |
| Social post exists at content/social/<slug>.md | No (warn only) |
| Article is on-niche for AI coding tools | Flag only |
Any FAIL = BLOCKED. All PASS = CLEAR TO PUBLISH.
Workflow position
quick-brief (/brief) → content-writer (/draft) → seo-auditor (/audit) → publishing-gate (/check) → social-writer (/social)
Output
A checklist table with PASS / FAIL / WARN per item, ending in either CLEAR TO PUBLISH or BLOCKED — fix N item(s) before publishing.