Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. Opt-in judgment; never edits code.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add GentBajko/capstone --skill review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gentbajko-review)More formats (shields.io, HTML) on the badges page.
---
name: review
description: Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. Opt-in judgment; never edits code.
---
# Capstone: review
From this skill's base directory, read `../core/references/core.md`
and `../core/references/core-authoring.md`, then execute
`../core/references/protocols/review.md`
exactly (review is core.md's sole judgment exception). No argument
runs both sides; `backend`/`be` or `frontend`/`fe` runs one.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
