mcpbeat

Code Review

owainlewis/code-review

Review code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes.

342 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
316
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/owainlewis/youtube-tutorials --skill code-review

The instruction itself

4 sections, as written by the author

Code Review

When reviewing code, follow this process:

Step 1: Understand the Change

Run git diff (or git diff --staged for staged changes) to see what changed.

Read the modified files in full to understand the surrounding context.

Step 2: Check for Issues

Review each changed file for:

Correctness

  • Logic errors, off-by-one errors, race conditions
  • Missing null/undefined checks at system boundaries
  • Incorrect error handling (swallowed errors, wrong error types)

Security

  • SQL injection, XSS, command injection
  • Hardcoded secrets or credentials
  • Overly permissive file/network access

Performance

  • N+1 queries, unnecessary loops, large allocations
  • Missing indexes for new database queries
  • Blocking operations in async code

Maintainability

  • Unclear naming, overly complex logic
  • Dead code, unused imports
  • Missing types in TypeScript

Step 3: Report

Format your review as:

  • Summary: One sentence on what the change does
  • Issues: Specific problems with file paths and line numbers
  • Suggestions: Optional improvements (clearly marked as optional)

Be direct. Don't pad with praise. Focus on things that matter.

How to use it

Copy the folder

Take owainlewis/code-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.