dev.review

Identify review types and apply personas to produce structured critiques.

21|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/kevinslin/skills --skill dev-review-kevinslin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev.review
Source: https://github.com/kevinslin/skills/tree/main/active/dev.review
Command: npx skills add https://github.com/kevinslin/skills --skill dev-review-kevinslin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill helps reviewers perform multi-type reviews (code, design docs, architecture, UX) by selecting the appropriate persona and generating structured critiques.

Core Features & Use Cases

  • Identify the review type from the artifact and user prompt.
  • Load the matching persona from references/persona-[review-type].md.
  • Apply the persona to the material and produce the review for deliverables like code, design docs, specs, architecture diagrams, and UX artifacts.
  • Example: Review a PR and provide a prioritized set of changes based on the code-review persona.

Quick Start

Review the latest PR or design doc using the appropriate persona and generate concrete, prioritized feedback.

Frequently Asked Questions about dev.review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate structured feedback for code and design doc reviews?▼

To generate structured feedback for code and design doc reviews, load a matching reviewer persona from reference files and apply it to the artifact to produce prioritized, concrete critiques.

What is a persona-based review and how does it work for architecture diagrams?▼

A persona-based review for architecture diagrams works by identifying the review type, loading a specific persona file from references, and applying that persona's perspective to generate structured, actionable feedback.

Can I use persona files to review UX artifacts across different projects?▼

Yes, you can use persona files to review UX artifacts across projects by loading the appropriate persona from references and applying it to generate structured critiques for the deliverable.

How do I set up persona files for multi-type reviews?▼

To set up persona files for multi-type reviews, create markdown files in the references directory formatted as persona-[review-type].md to define the specific criteria and perspective for each review type.

What types of artifacts can be reviewed using this persona-driven approach?▼

The persona-driven review approach can be applied to multiple artifact types including code, design docs, specs, architecture diagrams, and UX artifacts to produce prioritized feedback.

Do I need to manually select a reviewer persona for each pull request?▼

No, you do not need to manually select a reviewer persona for each pull request; the system identifies the review type from the artifact and user prompt to automatically load the matching persona.