mcpbeat Sign in

Code Review Agent Skill

Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output.

9k tokens
context cost
the whole folder, loaded on every use
10
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1313
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/microsoft/hve-core --skill code-review

What comes with it

33 915 bytes besides the instruction
references/context-bootstrap.md
references/cross-skill-forks.md
references/depth-tiers.md
references/dispatch-loop.md
references/emission-modes.md
references/lens-checklists.md
references/output-formats.md
references/severity-taxonomy.md
references/walkthrough-protocol.md

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

4 sections, as written by the author

Code Review — Skill Entry

This SKILL.md is the entrypoint for the Code Review skill.

The skill provides a reusable review workflow for orchestrators and perspective subagents that evaluate code changes across functional, standards, accessibility, PR, security, readiness, and full review perspectives. It centralizes change-brief preparation, review depth selection, severity normalization, and output contract details so that review agents stay thin and consistent.

Shared principles

Review work should stay anchored in evidence and should avoid premature conclusions. Keep the review grounded in file and line evidence, use proportional depth based on risk, read the full diff range before narrowing, and keep factual orientation separate from structured findings.

Normative references

  • Output Formats — reporting structure, merged report skeleton, and persisted artifact contract.
  • Severity Taxonomy — severity levels, verdict normalization, and risk classification.
  • Lens Checklists — perspective-specific review questions for functional, standards, accessibility, PR, security, and readiness reviews.
  • Context Bootstrap — Tier 0 procedure for proving the change surface, drafting a change brief, and scoping hotspots.
  • Depth Tiers — basic, standard, and comprehensive verification rigor dials.
  • Walkthrough Protocol — firm orientation floor, full-diff reading contract, and Register 1 narrative guidance.
  • Dispatch Loop — human-steered dispatch board, manifest schema, and walk-back loop contract.
  • Emission Modes — capability-gated dual-mode emission and persisted emission record.
  • Cross-Skill Forks — specialist review registry and collection-aware gating for follow-up reviews.

Skill layout

  • SKILL.md — this file (skill entrypoint).
  • references/ — durable review knowledge documents.
  • output-formats.md — output schema, report skeleton, and persistence behavior.
  • severity-taxonomy.md — severity and verdict normalization model.
  • lens-checklists.md — per-perspective review checklists.
  • context-bootstrap.md — Tier 0 context bootstrap and human-scoping workflow.
  • depth-tiers.md — Tier 1/2/3 verification-depth guidance.
  • walkthrough-protocol.md — orientation-first walkthrough contract and Register 1 narrative expectations.
  • dispatch-loop.md — dispatch board, manifest schema, and walk-back loop.
  • emission-modes.md — native and canonical emission strategies.
  • cross-skill-forks.md — specialist review registry and gating rules.

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take microsoft/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.