review skillA
review is agent-read markdown (skill) from gregkozakiewicz/roast-my-design-system: Review the UI and style files changed in the working tree against this repo's own design system, before they are saved or committed. Runs the same deterministic check as the CLI's --check flag (no tokens, about a second): hardcoded colours where a token exists, near-identical colour twins, off-scale spacing, radii, font sizes and shadows, typefaces outside the system, arbitrary Tailwind values, static inline styles, !important, duplicate component definitions, and on a repo built on MUI, Mantine.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Review my UI changes
You are checking the files that changed against the design system this repo already has. The engine does the judging; you explain the findings and help fix them.
## Steps
1. **Locate the repo root** (the directory with package.json; the current working directory unless the user pointed elsewhere). The check reads the git diff against HEAD plus untracked files, so it needs a git repository. If the user wants a different base (a branch, a commit), tell them the check compares with HEAD and suggest `git stash` or a branch checkout; do not fake it.
2. **Run the review** (deterministic, read-only, needs only Node 18 or newer):
```bash
node ${CLAUDE_SKILL_DIR}/../roast-my-design-system/scripts/review/index.mjs <repo-root>
```
`${CLAUDE_SKILL_DIR}` is this skill's own folder; the engine lives beside it in the roast skill's folder. Exit code 1 means findings, 0 means none. The output lists each changed file with its findings, a `Checked:` line naming every rule that ran, and a note for files left unjudged (email, print, artwork, pictures drawn with code).
…Read the whole file at its exact version.
How to install
mdr add gregkozakiewicz/roast-my-design-system/review@git:20260918.bb09ed1mdr add gregkozakiewicz/roast-my-design-system/review@sha256:39353ddab1b563a0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5dzs6n43r5fgnoiu)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3346 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gregkozakiewicz/roast-my-design-system · 25 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5dzs6n43r5fgnoiu GET https://markdownregistry.com/api/v1/resolve?ref=gregkozakiewicz/roast-my-design-system/review GET https://markdownregistry.com/api/v1/blob/39353ddab1b563a0b997ad1f3e2305c72fb46d649b1cc3b7a761bfe61922a30f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from gregkozakiewicz/roast-my-design-system
Every file in gregkozakiewicz/roast-my-design-system