← ClaudeAtlas

website-reviewlisted

The Double-Knuth review for a site — a two-pass correctness + cross-file consistency audit run at the END of a build (pre-launch) and after ADDING or substantially editing a page. Pass 1 = bugs/correctness (delegates the diff to /code-review); Pass 2 = completeness + route/URL/SEO/config/email/docs consistency against the site contract. Read-only: returns a ranked BUG/RISK/NIT list with file:line + fixes. Prerequisite: website-qa green. Also owns the "review depth" decision for website work — when this free default suffices vs. an owner-approved single external reviewer for genuinely higher-stakes changes (its "Review depth" section has the rule). Trigger phrases: "double-knuth", "double knuth the site", "review the site", "site review", "final review before launch", "review this page", "did adding the page break anything", "consistency check the site", "audit the site code", "how much review does this need", "do I need a second opinion on this", "should I use independent-review for this".
karero/website-builder · ★ 4 · Code & Development · score 74
Install: claude install-skill karero/website-builder
# Website review — Double-Knuth (correctness + consistency) A two-pass audit of a site's code/config/content, modelled on the `portfolio-code-reviewer` Double-Knuth. It sits **on top of `website-qa`**: the tests are the floor (must be green first); this is the human-grade review that catches what a test suite can't — cross-file drift and half-done work. ## When to run - **End of a build, before launch** (pipeline step 8). - **After adding or substantially editing a page** — a new route touches `PAGES`, nav, the sitemap, internal links and canonical, so consistency can silently break. - It is **read-only**: produce a ranked list, then fix BUGs before launch. Don't fix-and-forget — surface first (Rule 12: never hide a skipped or broken thing). - For just "is the offer clear to a stranger" on a site that's already built — faster and narrower than this full audit — use `website-positioning-check`. ## Review depth — the owner chooses, every time A website is lower-stakes than application code: a subtle bug in a landing page's copy costs a bad reading experience, not a broken payment or a data leak. This skill (Double-Knuth, below) is free, runs entirely in the current session, and is **the default, sufficient review for the large majority of website changes** — new pages, copy edits, layout tweaks, small SEO adjustments, content updates. An external AI reviewer on top of it is an *optional* extra, never a requirement, and never more than one at a time. **Default — no se