code-review

Reviews changed files in a session and attaches inline comments to code.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill code-review-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/src/vs/sessions/skills/code-review
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill code-review-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing every change in a coding session is time-consuming and easy to skip, letting bugs, security issues, and inconsistencies slip through. This Skill automates the review pass by inspecting the session's changed files and surfacing concrete, actionable issues directly on the code. ## Core Features & Use Cases - Changed-file detection: Uses git status and git diff to determine exactly which files changed in the current session. - Multi-dimension review: Checks correctness, edge cases, error handling, security, data handling, naming consistency, and test or documentation gaps. - Inline comments: Attaches each finding to the exact file URI and line range via the addComment tool, favoring fewer high-signal comments over stylistic nits. - Use Case: After finishing a feature branch, trigger the review from the Changes toolbar to get line-level feedback on bugs and missing error handling before committing. ## Quick Start Ask the agent to run a code review of the current session's changes and leave inline comments on any issues it finds.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a code review on my current changes?▼

Trigger the review via the Run Code Review button in the Changes toolbar. The agent detects changed files with git status and git diff, reviews each one, and leaves inline comments on the affected lines.

What kinds of issues does an automated code review catch?▼

It checks correctness and edge cases, bugs and regressions, missing error handling, security and data-handling problems, naming and consistency with surrounding code, and test or documentation gaps introduced by the change.

Does the code review modify my files or commit anything?▼

No. The review is read-only: it never edits files, runs commits, pushes, or performs any write operations. Its only output is review comments attached to specific file ranges.

Why does the review leave few comments on some files?▼

The reviewer prefers fewer, higher-signal comments over minor stylistic nits and does not comment on code that is already correct. A file with no comments means no concrete issues were found.

Can I customize the code review behavior?▼

Yes. You can customize the skill and save a copy to override the built-in behavior; deleting that copy restores the default review workflow.