review

Analyze code changes for quality, regression, documentation, and performance findings.

1|1|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/jiyeol-lee/dotfiles --skill review-jiyeol-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jiyeol-lee/dotfiles/tree/main/.opencode/skills/review
Command: npx skills add https://github.com/jiyeol-lee/dotfiles --skill review-jiyeol-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates and standardizes code-review analysis by assessing quality, regression risk, documentation gaps, and performance issues across changes.

Core Features & Use Cases

  • Focused Review Areas: Quality, Regression, Documentation, and Performance checklists to ensure comprehensive coverage.
  • File-by-File Findings: Present findings grouped by modified file with severity and actionable fixes.
  • Report Export: Produce a structured report suitable for PRs and team reviews.

Quick Start

Provide a complete, file-by-file code-review report for the given changes with severity-rated findings and suggested fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for a PR diff?

Automating code review for a PR diff involves analyzing modifications to detect quality, regression, documentation, and performance issues. This Skill evaluates code changes and generates a file-by-file report grouped by modified file, classifying findings by severity with actionable fix suggestions.

What is static analysis for regression risk in code changes?

Static analysis for regression risk identifies potential breakages in modified code without executing it. This Skill analyzes PR diffs or latest commits, categorizing regression findings by severity and providing structured, actionable fix suggestions to prevent defects in a file-by-file report format.

How do I generate a structured code review report for quality and performance?

Generating a structured code review report requires assessing quality and performance metrics across modified files. This Skill analyzes code changes, applies quality and performance checklists, and exports a standardized file-by-file report with severity-rated findings and suggested fixes suitable for team reviews.

Can I use automated code review on latest commits instead of full PR diffs?

Yes, automated code review can be applied to latest commits instead of full PR diffs. This Skill analyzes code changes from latest commits or branch diffs, evaluating quality, regression, documentation, and performance to present a file-by-file report grouped by modified file with severity-rated findings.

Does automated code review check documentation gaps and performance issues?

Yes, automated code review checks documentation gaps and performance issues. This Skill analyzes code changes using dedicated checklists to ensure comprehensive coverage, identifying missing documentation and performance bottlenecks, then classifying these findings by severity in a structured file-by-file report.