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.
How to install artifact-review?
olakunlevpn/olakunlevpn-artifact-skills/artifact-review
$npx -y skills add olakunlevpn/olakunlevpn-artifact-skills --skill artifact-reviewInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/olakunlevpn/olakunlevpn-artifact-skills" --skill "olakunlevpn/olakunlevpn-artifact-skills/artifact-review"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/olakunlevpn/olakunlevpn-artifact-skills" that are relevant to the current task. Run `npx skills add "https://github.com/olakunlevpn/olakunlevpn-artifact-skills"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
