code-reviewer

Analyze code submissions for bugs, standards, and security issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/paulund/skills --skill code-reviewer-paulund
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/paulund/skills/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/paulund/skills --skill code-reviewer-paulund

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews are essential for maintaining quality, catching issues early, and sharing knowledge across teams.

Core Features & Use Cases

  • Thoroughly analyze submissions for functionality, readability, and adherence to standards.
  • Identify potential bugs, architectural concerns, and security issues, providing actionable guidance.
  • Facilitate knowledge transfer by explaining design choices and suggested improvements.

Quick Start

Review the submitted code by listing issues, offering concrete improvements, and outlining acceptance criteria.

Frequently Asked Questions about code-reviewer

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

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

Actionable code review feedback requires a structured checklist to analyze submissions for functionality, readability, and standards. Reviewers should list issues, offer concrete improvements, and outline clear acceptance criteria aligned with project guidelines.

What should a code review checklist include for security and maintainability?

A code review checklist for security and maintainability should include identifying potential bugs, architectural concerns, and security issues. It must verify adherence to design patterns and project guidelines while providing actionable guidance for improvements.

Does code review feedback help enforce design patterns across teams?

Code review feedback helps enforce design patterns across teams by thoroughly analyzing submissions for adherence to standards. It facilitates knowledge transfer by explaining suggested improvements and architectural choices during reviews.

How do I review code submissions for architectural concerns and bugs?

To review code submissions for architectural concerns and bugs, analyze the code thoroughly against project guidelines and design patterns. Identify potential issues and provide actionable guidance with concrete improvements and acceptance criteria.

What is the best way to structure pull request review feedback for knowledge transfer?

The best way to structure pull request review feedback is listing issues, offering concrete improvements, and outlining acceptance criteria. This approach facilitates knowledge transfer by explaining design choices and suggested improvements clearly.