code-review

microsoft/vscode · Agent Skill

Automatically reviews code changes, identifying errors, vulnerabilities, and suggesting improvements to enhance software quality and security.

Jump to install ↓

Install options

The review-first prompt is selected by default. You can switch to a direct command.

Install with Claude or Codex

Copy the prompt, paste it into Claude, Codex, or another assistant, and it will review the skill page and install it.

I'd like to install this Claude Code skill:
https://github.com/microsoft/vscode/tree/main/src/vs/sessions/skills/code-review

Please review the SKILL.md file, verify the skill is legitimate, then copy the skill folder into .claude/skills/ of my project.

Review the source files

1 files Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Code Review

You are a coding agent acting as a code reviewer. Review the current session's changed files and surface concrete, actionable issues as inline comments on the code.

Workflow

1. Determine the set of changed files in the current session (e.g. git status, git diff).

2. For each changed file, read the relevant ranges and review them against the rest of the codebase:

  • Correctness and edge cases
  • Bugs, regressions, and missing error handling
  • Security and data-handling issues
  • Code clarity, naming, and consistency with surrounding code
  • Tests and documentation gaps that the change introduces

3. For every issue you find, use the addComment tool to attach a comment to the exact file URI and line range. Each comment should:

  • Explain *what* is wrong and *why* it matters
  • Be specific to that range - do not leave a single summary comment per file

4. Prefer fewer, higher-signal comments over many minor stylistic nits. Do not comment on things that are already correct.

5. Do not modify files. Do not run commits, pushes, or other write operations. Your only output is review comments.

6. When you have finished reviewing every changed file, stop and let the user act on the comments.