code-review
/code-review
Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.
- Author
- microsoft ↗
- Repository
- vscode ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.
Original author description
Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.
How it works
- Establish the Review Scope
- Review the Changes
- Report Findings
SKILL.md preview
--- name: code-review description: Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review. --- # Code Review Review the proposed changes as a senior maintainer. Focus on actionable defects introduced by the changes, especially correctness issues, regressions, and changes that are not necessary for the stated goal. ## Establish the Review Scope Before reviewing: 1. Determine the intended change from the request, pull request description, linked issue, and maintainer comments. 2. Identify the complete diff against the appropriate base. 3. Account for every changed file and subsystem. Do not infer the purpose solely from the implementation. If the intended behavior is unclear, state the assumption used for the review. ## Review the Changes Trace the changed behavior through its callers, dependencies, and tests. Check for: - Incorrect logic, broken edge cases, or behavior that contradicts the stated goal. - Regressions in existing behavior, including platform-specific and lifecycle behavior. - Missing or incorrect error handling. - Unsafe assumptions about data, ordering, concurrency, or object lifetime. - Tests that do not cover the changed behavior or that would pass without the fix. - Changes whose connection to the stated goal is unclear. Keep fixes tied to the underlying cause. Do not accept unrelated changes to behavior, state management, or architecture merely because they make the reported symptom disappear. Treat prerequisite or tightly coupled changes as in scope only when their necessity is clear from the implementation or pull request description. A changed file should be necessary for the stated goal or be a directly related test, documentation update, generated artifact, or required refactor. Independent cleanup and speculative improvements belong in a separate change. ## Report Findings Report only findings that are: - Introduced or made materially worse by the changes under review. - Specific and actionable. - Supported by the code or by a concrete missing validation. For each finding: 1. State the user-visible or engineering impact. 2. Explain the conditions that trigger it. 3. Point to the smallest relevant changed line or range. 4. Explain why the current implementation is incorrect. Prioritize findings by severity. Do not report stylistic preferences, speculative concerns, or pre-existing problems unrelated to the change. If no actionable findings remain, say so explicitly and mention any meaningful validation gaps. Flag changes whose connection to the stated goal is unclear even when tests pass or the resulting behavior appears correct. Ask for the causal link to be explained; if none exists, recommend reverting the change or moving it to a separate pull request.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · microsoft/vscode | 90 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5a99a2b065fd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90code-review-and-quality
Reviews a diff for correctness, risk, and missing evidence before merge. Use when preparing a change for commit, reviewing a pull request, reviewing AI-generated code, or deciding whether work is genuinely done. - 80Code review
Review a diff or module for correctness, security, regressions, and missing tests. Use when the user asks for a review or before shipping a change. - 90wasp-review
Review code changes for correctness, clarity, and potential issues. Use when the user asks for a review, code review, PR review, or wants feedback on a diff or file. - 90review-a-pull-request
A careful code review of a change, a branch or a pull request: correctness, tests, security, readability, with findings ordered by how much they matter. Use when the owner asks you to review code, a diff, a branch or a PR. - 100awesome-code-review
Reviews a diff, patch or pull request for correctness, security and team standards, with severity-ranked findings. Use when asked to review a change or PR, or before merging. - 100audit-code-review
Review a PR or diff for correctness, security, and maintainability. Use for a pull request, a named change set, or "review my changes". Repo-wide anti-patterns → audit-code-quality. Bulk transforms → audit-codemod-safety.