dev-code-reviewer

Guide structured code reviews with quality thresholds and feedback guidelines.

5|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill dev-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-code-reviewer
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/dev-code-reviewer
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill dev-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to performing and receiving effective code reviews, ensuring higher code quality, identifying critical issues early, and fostering better collaboration.

Core Features & Use Cases

  • Structured Review Process: Outlines a step-by-step process from pre-review checklists to review verdicts.
  • Quality Thresholds & Antipatterns: Defines clear quality metrics and common code smells to watch out for.
  • Feedback Guidelines: Offers best practices for both giving and receiving code review feedback constructively.
  • Use Case: A developer is about to submit a pull request and wants to ensure it meets quality standards. They consult this Skill for a pre-review checklist and guidance on how to structure their changes for optimal review.

Quick Start

Consult the Dev-Code-Reviewer skill for guidance on how to conduct a thorough code review.

Frequently Asked Questions about dev-code-reviewer

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

FAQPage Schema
How do I perform a systematic code review to identify architectural flaws and security vulnerabilities?

A systematic code review involves a structured process from pre-review checklists to review verdicts. It evaluates code maintainability, correctness, and security to identify architectural flaws, logic errors, and vulnerabilities early.

What are the common code antipatterns and quality thresholds to watch for during software development?

Common code antipatterns are stylistic inconsistencies, performance bottlenecks, and structural code smells. Quality thresholds define clear metrics to detect these issues, ensuring higher maintainability and preventing critical flaws from reaching production.

What is the best way to give and receive constructive code review feedback in a development team?

The best way to give and receive code review feedback is by following established feedback guidelines. This fosters better collaboration among software development teams by ensuring exchanges remain constructive and focused on code quality.

How do I use a pre-review checklist before submitting a pull request for quality assurance?

To use a pre-review checklist before submitting a pull request, consult a structured review framework. It helps you verify that changes meet quality standards, avoid logic errors, and structure modifications for optimal team assessment.

When do I need a structured code review process for my software development project?

You need a structured code review process when aiming to improve code maintainability, correctness, and security. It is essential for software development teams wanting to enforce best practices and identify performance bottlenecks early.