code-review

Review pull requests for correctness, style, security, and architecture.

2|1|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/leynos/agent-helper-scripts --skill code-review-leynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/leynos/agent-helper-scripts/tree/main/skills/code-review
Command: npx skills add https://github.com/leynos/agent-helper-scripts --skill code-review-leynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss defects or drown in noise. This Skill provides structured, actionable guidance to help reviewers catch real problems, enforce quality standards, and transfer knowledge.

Core Features & Use Cases

  • Context-driven checks: Prepares the reviewer with sources like PR description, neighbouring files, and CI expectations to evaluate intent and conformance.
  • Architectural & style alignment: Evaluates against project conventions, design docs, and workflow expectations to ensure consistency.
  • Actionable feedback workflow: Produces clear, prioritized recommendations and follow-up steps to communicate decisions effectively.
  • Use Case: Use during feature additions, refactors, or critical fixes to maintain code health across the repository.

Quick Start

Review the current branch against its base, assess context, and generate structured feedback in under five minutes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a structured code review that catches real issues in pull requests?

A structured code review gathers context from PR descriptions, neighboring files, and CI expectations, then evaluates correctness, style, security, and architecture to identify real issues and produce actionable feedback.

What does context-driven code review check for beyond basic code correctness?

Context-driven code review checks for correctness alongside style consistency, security vulnerabilities, and architectural alignment, enforcing conformance with project standards, design documents, and workflow expectations.

Can I use this code review process for bugfix audits and refactors, not just new features?

Yes, this code review process applies to feature additions, bugfix audits, refactors, and general contributions, maintaining code health and enforcing quality standards across the repository.

What's the best way to align code review feedback with project conventions and design documents?

The best way to align feedback with project conventions is to evaluate pull requests against AGENTS.md, .rules/*, and design documents, ensuring the review enforces architectural and style alignment.

How do I prioritize code review recommendations to avoid drowning pull requests in noise?

To avoid noise, generate structured critique with clear, prioritized recommendations and follow-up steps, focusing on traceable references to project standards rather than subjective opinions.

When should I not rely on automated code review guidance for pull requests?

You should not rely solely on automated guidance when a pull request lacks clear context, such as missing PR descriptions, absent design documents, or undefined project standards, as effective review requires context-rich inputs.