code-review

A review of the code you just changed, delivered as notes attached to the exact lines they concern rather than as one lump of feedback at the end.

WHEN TO USE

SCOPE

USE FOR

Check a change for edge cases and for naming that clashes with the code around it.
Catch bugs, missing error handling, or security issues before you commit.
Find test or documentation gaps that a change introduces without writing them yourself.

NOT FOR

Fixing the issues it finds or making a commit — it only leaves review comments.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (2)

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

Determine the set of changed files in the current session (e.g. git status, git diff).
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
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
Prefer fewer, higher-signal comments over many minor stylistic nits. Do not comment on things that are already correct.
Do not modify files. Do not run commits, pushes, or other write operations. Your only output is review comments.
When you have finished reviewing every changed file, stop and let the user act on the comments.

Built into VS Code. Nothing to install there. The npx skills add command copies the same instructions into another agent, but they are written for VS Code and may call tools only VS Code has.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add https://github.com/microsoft/vscode/tree/main/src/vs/sessions/skills/code-review

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

View on GitHub

Same repository

act-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.Read full description
agent-customization
**WORKFLOW SKILL** — Create, update, review, fix, or debug VS Code agent customization files (.instructions.md, .prompt.md, .agent.md, SKILL.md, copilot-instructions.md, AGENTS.md). USE FOR: saving coding preferences; troubleshooting why instructions/skills/agents are ignored or not invoked; configuring applyTo patterns; defining tool restrictions; creating custom agent modes or specialized workflows; packaging domain knowledge; fixing YAML frontmatter syntax. DO NOT USE FOR: general coding questions (use default agent); runtime debugging or error diagnosis; MCP server configuration (use MCP docs directly); VS Code extension development. INVOKES: file system tools (read/write customization files), ask-questions tool (interview user for requirements), subagents for codebase exploration. FOR SINGLE OPERATIONS: For quick YAML frontmatter fixes or creating a single file from a known pattern, edit the file directly — no skill needed.Read full description
author-contributions
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.Read full description
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.Read full description
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.Read full description
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-*.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating user timing marks.Read full description

Code Review

Workflow

No requirements beyond installing this skill were found.

More skills

act-on-feedback

agent-customization

author-contributions

chronicle

commit

cpu-profile-analysis