artifact-review
Skill4 starsChanged 6 months agoNo licenceView on GitHub
OUTPUT IS ALWAYS A `.html` FILE (never `.md`, never plain markdown). Use this skill whenever the user asks for a code review writeup, PR review, annotated diff, "review this patch", "give feedback on this change", "leave inline comments on this PR", "summarize what's wrong with this code", or any reviewer-side artifact that pairs concrete diff hunks with human commentary, suggestions, and approve/request-changes verdicts as a polished HTML document. This is the reviewer-side companion to `artifact-report`'s PR writeup (which is author-side). Pair with `artifact-css` for the underlying design system. Do NOT use for casual one-line feedback or for purely conversational review chats — only when an HTML artifact with annotated diffs is the deliverable.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- aigengame/skillstheir own version, first seen Oct 17, 2026
- tsingyuai/scientifytheir own version, first seen Oct 8, 2026
- ifoohoo/artifact-chain-assistanttheir own version, first seen Aug 12, 2026
- arDaraz/artifact-reviewtheir own version, first seen Aug 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- tsingyuai/scientify★ 2.2ksame name
- aigengame/skills★ 2same name
- arDaraz/artifact-review★ 1same name
- ifoohoo/artifact-chain-assistant★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- artifact-cssSkill
- artifact-deckSkill
- artifact-designSkill
- artifact-diagramSkill
- artifact-editorSkill
- artifact-explainerSkill
- artifact-flowSkill
- artifact-planSkill
- artifact-reportSkill
- artifact-sandboxSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.