code-review

Name: code-review
Availability: InStock
Author: Paulund

Review code and pull requests using structured checklists and severity-categorized feedback.

Updated Aug 23, 2026

Search Tags:#quality assurance #code review #best practices #debugging #frontend #software development #backend

Ready to run

npx skills add https://github.com/paulund/ai --skill code-review-paulund

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/paulund/ai/tree/main/code-review/skills/code-review
Command: npx skills add https://github.com/paulund/ai --skill code-review-paulund

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring higher code quality, identifying bugs early, and promoting best practices across development teams.

Core Features & Use Cases

Structured Feedback: Provides actionable feedback categorized by severity (Critical, High, Medium, Low).
Comprehensive Checks: Guides reviewers on what to look for, including correctness, security, performance, architecture, and test coverage.
Use Case: When a pull request is submitted, use this Skill to generate a detailed review checklist and identify potential issues before merging.

Quick Start

Use the code-review skill to analyze the provided code snippet for potential issues.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I conduct a systematic code review for a pull request?▼

To conduct a systematic code review, use this Skill to generate a structured checklist that evaluates correctness, security, performance, architecture, and test coverage. It provides actionable feedback categorized by severity to identify potential issues before merging.

What should I look for when reviewing frontend and backend code quality?▼

When reviewing frontend and backend code quality, you should check for correctness, security vulnerabilities, performance bottlenecks, architectural flaws, and adequate test coverage. This Skill leverages reference guides to guide reviewers through these specific checks.

Can I get actionable feedback on code bugs and best practices before merging?▼

Yes, you can get actionable feedback on code bugs and best practices before merging. This Skill categorizes feedback by severity—Critical, High, Medium, and Low—to help you identify bugs early and promote best practices across your development team.

What is the best way to structure pull request reviews for software development?▼

The best way to structure pull request reviews for software development is to use a systematic process with categorized feedback. This Skill provides a detailed review checklist addressing correctness, security, performance, architecture, and test coverage requirements.

Does this code review process support both frontend and backend development?▼

Yes, this code review process supports both frontend and backend development. It addresses specific quality assurance, debugging, and best practices requirements across both domains to ensure comprehensive code quality evaluation.