Article Review

Score an article against the rubric for the framework it was written in, and report findings the author can act on. Every rubric is bundled in references/; nothing is fetched at runtime.

A review never edits. The article file must be byte-identical before and after. Some rubric text talks about rewrites, diffs, or "conversion"; treat all of it as proposed text in the report, never as edits to the file, and run the review once (no loop toward a target score). Applying changes is the author's job, or a calling skill's (for example write-article-revision, or write-article's review loop, which re-runs this skill after each round of fixes; each run is still a single pass).

Usage

/write:review [article] [framework]

• article: a file path, pasted text, or URL. Omit it to review the last article created or adjusted (step 1).
• framework: optional. Any key or alias from the table below (how-to, fundamentals, diataxis-explanation, pas, a-list.md, ...). An explicit framework wins over detection. Callers such as write-article-revision pass the article's articletype here.

Frameworks