code-reviewer

Reviews diffs and pull requests against repository style rules and correctness checks.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill code-reviewer-eklyukin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill code-reviewer-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews are inconsistent when reviewers rely on memory alone, missing security issues, correctness bugs, or violations of team style standards. This Skill provides a structured checklist that applies the repository's own code-style rules plus general correctness and security checks to every diff or pull request. ## Core Features & Use Cases - Standards-based review: Applies the checks from rules/code-style.md, including Boy Scout Principle, SOLID, YAGNI, DRY, and testability. - Correctness and security checklist: Catches boundary errors, swallowed exceptions, injection risks, hardcoded secrets, race conditions, and missing test coverage. - Severity-ranked output: Reports findings grouped into Must fix, Should consider, and Nit sections with file and line references. - Use Case: Before merging a pull request, run this Skill on the PR diff to get a ranked list of issues, such as an unparameterized SQL query flagged as Must fix and a premature abstraction flagged as Should consider. ## Quick Start Review the current git diff against the repository code-style rules and report any correctness or security findings ranked by severity.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a pull request against team coding standards?▼

Run the review on the PR diff rather than just file names, then walk a checklist covering your style rules plus correctness and security items. Report findings ranked by severity with file and line references so authors can prioritize fixes.

What should a code review checklist include?▼

A solid checklist covers style principles like SOLID, DRY, and YAGNI, plus correctness items like boundary conditions, error handling, injection risks, hardcoded secrets, concurrency issues, and whether tests cover real edge cases.

How to check a diff for security issues before merging?▼

Inspect the diff for injection risks such as string-built SQL or shell commands, hardcoded credentials or tokens, missing input validation at trust boundaries, and silently swallowed errors. Flag each finding with its file and line number.

Does this code review approach work for any programming language?▼

Yes, the checklist is language-agnostic. Style principles like SOLID and DRY and security checks like injection and secret detection apply regardless of language, while the repository's own code-style rules supply language-specific standards.

When should review findings be omitted from the report?▼

Omit a severity section entirely when it has no findings rather than writing filler like "Must fix: none". If nothing substantial was found, say so directly instead of padding the review with nitpicks.