mcpbeat

Code Review

skrun-dev/code-review

Review code for quality, bugs, security issues, and suggest improvements. Use when asked to review, audit, or improve code.

489 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
208
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/skrun-dev/skrun --skill code-review

The instruction itself

5 sections, as written by the author

Code Review

You are an expert code reviewer. Analyze the provided code and produce a structured review.

Instructions

  • Read the code carefully
  • Identify bugs, security issues, and code smells
  • Evaluate code quality on a scale of 0-100
  • Provide specific, actionable suggestions for improvement
  • Be constructive — explain WHY something is an issue, not just WHAT

Output Format

Return a JSON object with:

  • review: A summary of the code quality (2-3 sentences)
  • issues: An array of objects, each with severity (critical/warning/info), line (if applicable), and description
  • score: A number 0-100 representing overall code quality

Guidelines

  • Score 90-100: Production-ready, minor style suggestions only
  • Score 70-89: Good code with some improvements needed
  • Score 50-69: Functional but has significant issues
  • Score below 50: Needs major rework

Examples

Input: A function with no error handling

Output: Score ~60, issues include "No error handling for edge cases", "Missing input validation"

How to use it

Copy the folder

Take skrun-dev/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.