code-review

Review code changes for quality, correctness, and maintainability using a structured checklist.

Updated May 15, 2021
One-click install
npx skills add https://github.com/JustinFirsching/dotfiles --skill code-review-justinfirsching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/JustinFirsching/dotfiles/tree/main/opencode/.config/opencode/skill/code-review
Command: npx skills add https://github.com/JustinFirsching/dotfiles --skill code-review-justinfirsching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic checklists and guidance to ensure code changes meet quality, correctness, and maintainability standards. This helps teams avoid defects, reduce review time, and improve code health.

Core Features & Use Cases

  • Structured Review Process: Understand context, read the code, check for correctness, evaluate quality, and provide actionable feedback.
  • Actionable Feedback Guidance: Use labeled feedback like [blocking], [important], and [nit] to prioritize issues clearly.
  • Checklist-based Verification: Covers Correctness, Error Handling, Readability, Maintainability, Performance, Testing, API Design, Security, Concurrency, Observability, Dependencies, and Backward Compatibility.

Quick Start

Run the code-review workflow on the latest PR and apply the checklist to generate structured, actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I provide structured code review feedback on a pull request?

To provide structured code review feedback on a pull request, apply a systematic checklist covering correctness, error handling, and security, then prioritize issues using labeled tags like [blocking], [important], and [nit] for actionable notes.

What should be included in a software engineering code review checklist?

A software engineering code review checklist should include verification of correctness, readability, maintainability, performance, testing, API design, security, concurrency, observability, dependencies, and backward compatibility to ensure comprehensive code health.

How can I enforce consistent code quality and maintainability standards across patches?

You can enforce consistent code quality and maintainability standards across patches by utilizing a structured review process that reads code context, checks for correctness, evaluates quality, and generates prioritized, actionable feedback.

What is the best way to prioritize issues found during a code review?

The best way to prioritize issues found during a code review is to label feedback by severity using tags like [blocking] for critical defects, [important] for major improvements, and [nit] for minor suggestions, ensuring clear issue prioritization.

Does this code review process work with modern development workflows and diffs?

Yes, this code review process works directly with modern development workflows, applying its structured checklist to pull requests, patches, and diffs to produce consistent and actionable feedback.