mcpbeat

Code Review

microsoft/vscode-containers-code-review

Review a pull request in this repository (the vscode-containers / Container Tools extension) when the automated reviewer has already supplied the diff and changed files. Checks localization, async/resource correctness, TypeScript conventions, command-line construction, telemetry, settings, and cross-platform issues distilled from this repo's review history. For an on-demand review by PR number, URL, or current branch, use review-pr instead.

4k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
134
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/vscode-containers --skill code-review

What comes with it

15 709 bytes besides the instruction
rubric.md

The instruction itself

1 sections, as written by the author

Container Tools code review

Apply the shared grading rubric in rubric.md to the pull request under

review. That file is the single source of truth for what to look for and how to grade it --

read it and follow it.

This skill is for the automated review context, where the pull request's diff and changed files

are already provided and review comments are published through the normal review mechanism. If

that context is not present, use review-pr instead. So:

  • Do not fetch the PR yourself or run gh -- work from the diff you were given.
  • Do not approve. Leave comments / request changes only; approval is a human decision.
  • Focus your comments on the changed lines. Ground every point in the diff or a concrete repo

convention, and cite the exact helper or pattern the author should use instead of a generic

complaint.

  • Prefer high signal, low noise: raise real, high-confidence issues; route genuine "did you

intend X" points as questions rather than assertions; drop speculation.

Follow the rubric's severity/confidence grading and the "What NOT to flag" list so the review

stays useful and does not bury maintainers in nits.

How to use it

Copy the folder

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