skills.rest
lukeylias
lukeyliasCOMMUNITY
Explore all skills by this author →
GitHub

review

Review files, diffs, and documents to surface severity-ranked issues.

Updated Apr 25, 2026
Search Tags:#code review#analysis#review#issues#document review#git diff#severity
One-click install
npx skills add https://github.com/lukeylias/lukeydev --skill review-lukeylias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lukeylias/lukeydev/tree/main/skills/review
Command: npx skills add https://github.com/lukeylias/lukeydev --skill review-lukeylias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect code, diffs, and documents with fresh eyes so you can catch bugs, ambiguities, and risky assumptions before they cause problems.

Core Features & Use Cases

  • Targeted review: Analyze a single file, a git diff, or a planning document based on what the user points to.
  • Issue-first feedback: Focus on problems, edge cases, missing validation, inconsistencies, and unclear requirements rather than praise.
  • Severity-ranked output: Present findings in a structured table with impact so the most important problems are easy to act on.
  • Use case: A developer asks for a PRD review before implementation, and this Skill surfaces ambiguous scope, missing edge cases, and conflicting requirements.

Quick Start

Ask the Skill to review the file, diff, plan, or spec you want checked and it will return prioritized issues with concise explanations.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a git diff to find issues before merging?▼

To review a git diff, point the Skill to your changes and it returns severity-ranked findings with file and line references, concise impact explanations, and a brief overall assessment.

Can I use this to review a PRD or planning document for missing requirements?▼

Yes, you can review a PRD or spec to surface ambiguous scope, missing edge cases, and conflicting requirements. It applies fresh eyes to planning documents to catch issues before implementation.

What is the best way to get severity-ranked feedback on code changes?▼

The best way to get severity-ranked feedback is to request an issue-first review of your files or diffs, which focuses on problems, edge cases, and missing validation in a structured table format.

Does the code review output include specific file and line references?▼

Yes, the code review output includes specific file and line references for each finding. This ensures actionable issues are easy to locate and act on within your original source files.

How do I analyze a single file for bugs and risky assumptions?▼

To analyze a single file, ask the Skill to review it and it will apply targeted issue-first feedback to identify bugs, risky assumptions, and missing validation before they cause problems.

Related Skills

Explore More Software Engineering Skills→
JayRHaJayRHa
3

code-reviewer

Review code diffs and PRs for correctness, security, and maintainability.

Community
Intermediate
SDDKKKSDDKKK

brainstorm

Generate structured PRD files through AI-guided collaborative brainstorming.

Community
Advanced
haojing8312haojing8312
154

requesting-code-review

Analyze git diff ranges and categorize issues by severity for code review.

Community
Intermediate
cloudvoyantcloudvoyant

review

Validate code compliance with style guides and best practices.

Official
Advanced