Review code changes from multiple perspectives with context bootstrap, depth-tier rigor, and structured findings output.
npx skills add https://github.com/microsoft/hve-core --skill code-review
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.
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.
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.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
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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
Comprehensive GitHub code review with AI-powered swarm coordination
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.
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.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
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.
Take microsoft/code-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.