roast-my-design-system 8.3.2 → 8.4.0

package/README.md

@@ -8,7 +8,7 @@
 
 ## Your AI can write the UI. This makes sure it writes *your* UI.
 
-A free CLI tool (and Claude Code skill) that roasts your repo's design system with real data, then generates the rules that keep your AI agent on-system.
+A free CLI tool, and a Claude Code plugin with two skills and a bundled local MCP server, that roasts your repo's design system with real data, reviews what you change against it, and generates the rules that keep your AI agent on-system.
 
 > **New in 8.0: support for the four big component kits.**
 >
@@ -83,6 +83,7 @@ Type these in a terminal and you get a result.
 | `... --card` | `roast-card.svg`: a shareable 1200x630 card with the score and worst findings. Pure SVG, embeds in a README |
 | `... --sarif` | `design-system-roast.sarif` for GitHub code scanning: upload it in CI and findings appear in the Security tab, annotated on files |
 | `... --check` | The working tree's changed files checked against the design system, in the terminal. Exits 1 on findings, so it slots into scripts |
+| `/roast-my-design-system:review` (in Claude Code) | The same check in chat, from the plugin's second skill: each changed file's findings with the fix named, then the fixes applied and the check re-run |
 | <code>...&nbsp;--exclude&nbsp;lab/</code> | Leave a folder out of the scan (repeat the flag or comma-separate). Or list folders in a `.roastignore` file at the repo root. Either way the report says so in the header; see [Scoping the scan](#scoping-the-scan) |
 | `... --json` | The scan summary as JSON on stdout, for scripts and pipelines. Includes `schemaVersion`, the benchmark used, and every metric as a number, so two scans can be compared |
 | <code>...&nbsp;--by&nbsp;"Dwayne&nbsp;Hicks"</code> | Puts a name in the report header, for when you ran it for someone else |
@@ -269,16 +270,18 @@ Run it inside any repo. Same scanner, same report, straight from npm. The Claude
 /plugin install roast-my-design-system@roast-my-design-system
 ```
 
+What it installs: two skills and one local MCP server, nothing else. **roast** (`/roast-my-design-system`, or "roast my design system") scans the whole repo and writes the report with Claude's read of the numbers inside it, then walks the fixes with you. **review** (`/roast-my-design-system:review`, or "review my UI changes") checks only what changed, in about a second. The bundled server gives your agent five read-only tools while it writes UI. Local, no network, no telemetry.
+
 If those commands error, your Claude Code is likely older than the plugin marketplace feature. Update Claude Code and retry, or use the manual route below: it works everywhere and installs the same skill.
 
 **Manual (Claude Code, any version):**
 
 ```bash
 git clone https://github.com/gregkozakiewicz/roast-my-design-system.git
-cp -r roast-my-design-system/skills/roast-my-design-system ~/.claude/skills/
+cp -r roast-my-design-system/skills/roast-my-design-system roast-my-design-system/skills/review ~/.claude/skills/
 ```
 
-(Use `.claude/skills/` inside a repo instead to share it with your team.)
+(Use `.claude/skills/` inside a repo instead to share it with your team. The `review` skill needs the `roast-my-design-system` folder beside it; it runs the engine from there.)
 
 **OpenAI Codex CLI** (same SKILL.md, same folder):
 
@@ -301,6 +304,14 @@ Open Claude Code in the repo you want roasted and type:
 /roast-my-design-system
 ```
 
+And once you have a design system worth protecting, the second skill checks only what you changed, in about a second:
+
+```
+/roast-my-design-system:review
+```
+
+It runs the same check as `--check` on the files in your git diff and lists each finding with its fix, in the kit's own vocabulary on a MUI, Mantine, Chakra, Ant Design or Tailwind-theme repo. No score, no report: the small check for Tuesday afternoons. Claude also picks it up from plain words such as "review my UI changes" or "did I break the design system".
+
 You get the roast in chat plus `design-system-roast.html` at your repo root: a self-contained page (open it, Slack it, email it, no external requests) with:
 
 - a **health score** computed from how your numbers sit against the ideal
@@ -331,6 +342,12 @@ With the MCP server connected (see [Live answers over MCP](#live-answers-over-mc
 Is there already a Button component in this repo, and which one should I use?
 ```
 
+And the everyday one, after you have changed some UI:
+
+```
+Review my UI changes against the design system.
+```
+
 ## Troubleshooting
 
 - **"Command not found" or the plugin will not install.** Update Claude Code; the plugin marketplace needs a recent version. The manual install above works on any version.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "roast-my-design-system",
-  "version": "8.3.2",
+  "version": "8.4.0",
   "mcpName": "io.github.gregkozakiewicz/roast-my-design-system",
   "description": "Your AI can write the UI. This makes sure it writes your UI. A deterministic scanner scores your design system 0-100 against 112 public repos, reads React and web components (Stencil, Lit), hands you a copy-paste fix prompt for each top finding, writes rules for Claude, Cursor, Copilot and Windsurf with --apply, and runs as a local MCP server with --mcp.",
   "keywords": [

package/skills/roast-my-design-system/scripts/lib/version.mjs

@@ -1,7 +1,7 @@
 // Single version constant for the engine — imported by diagnose (report
 // footer) and rules (generated-by line). This is the bump spot that used to
 // live as a const inside diagnose/index.mjs.
-export const VERSION = '8.3.2';
+export const VERSION = '8.4.0';
 // The shape of harvest.json and summary.json. Bumped only when a field is
 // renamed, removed or changes meaning; a new field is not a new schema. A
 // tool comparing two scans compares like with like by this number, not by VERSION.

package/skills/roast-my-design-system/scripts/review/index.mjs

@@ -0,0 +1,23 @@
+#!/usr/bin/env node
+/**
+ * The review, standalone: the working tree's changed UI and style files
+ * (git diff plus untracked) judged against the design system the scan found.
+ * Same engine and same words as roast_review over MCP and `--check` on the
+ * CLI; this entry exists so the review skill can run it from its own folder
+ * without the npm launcher. Read-only. Exits 1 when there are findings, so a
+ * script can gate on it.
+ *
+ *   node review/index.mjs <repo-root> [--json]
+ */
+import { resolve } from 'node:path';
+import { loadKnowledge } from '../mcp/knowledge.mjs';
+import { reviewData } from '../mcp/tools.mjs';
+import { VERSION } from '../lib/version.mjs';
+
+const argv = process.argv.slice(2);
+const asJson = argv.includes('--json');
+const root = resolve(argv.find((a) => !a.startsWith('--')) ?? '.');
+const { text, total } = reviewData(loadKnowledge(root));
+if (asJson) console.log(JSON.stringify({ version: VERSION, root, findings: total, text }, null, 2));
+else console.log(text);
+process.exit(total ? 1 : 0);