agent-customization
**WORKFLOW SKILL** — Create, update, review, fix, or debug VS Code agent customization files (.instructions.md, .prompt.md,…
@microsoftInstall SkillDevelopment
Skill
/code-review
Perform a code review of the current session's changes. Use when the user requests a code review via the Run Code Review button in the Changes toolbar.
Claude Code
$ npx -y skills add microsoft/vscode --skill code-review --agent claude-code
Codex
$ npx skills add microsoft/vscode --skill code-review -a codex -y
Cursor
$ npx skills add microsoft/vscode --skill code-review -a cursor -y
Gemini CLI
$ npx skills add microsoft/vscode --skill code-review -a gemini-cli -y
GitHub Copilot
$ npx skills add microsoft/vscode --skill code-review -a github-copilot -y
OpenCode
$ npx skills add microsoft/vscode --skill code-review -a opencode -y
Windsurf
$ npx skills add microsoft/vscode --skill code-review -a windsurf -y
SKILL.md
code-review.SKILL.mdname: code-review
description: Perform a code review of the current session's changes. Use when the user requests a code review via the Run Code Review button in the Changes toolbar.
<!-- 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.
Read more
name: code-review description: Perform a code review of the current session's changes. Use when the user requests a code review via the Run Code Review button in the Changes toolbar.
<!-- 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.
Stats
195,355
Stars
43,822
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
195k26 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 195.3k
Other skills on vscode.
@microsoftInstall Skillchronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks…
@microsoftInstall Skillcreate-canvas
Create a Copilot extension canvas at user, workspace, or plugin scope.
@microsoftInstall Skillcreate-hook
Create a hook (.json) to enforce policy or automate agent lifecycle events.
@microsoftInstall Skillcreate-instructions
Create an instructions file (.instructions.md) for a project rule or convention.
@microsoftInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about code-review.
- Which coding agents can use code-review?
- code-review installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.