skills.rest
vinhnx
vinhnxCOMMUNITY
Explore all skills by this author →
Website𝕏@vinhnxGitHub

cmd-review

Reviews the current diff or selected files for bugs, regressions, and missing tests.

829|80|Updated Aug 29, 2025
Search Tags:#Git#regression#diff#slash command#Code review#Review#Code quality
One-click install
npx skills add https://github.com/vinhnx/VTCode --skill cmd-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmd-review
Source: https://github.com/vinhnx/VTCode/tree/main/crates/codegen/vtcode-skills/src/skills/assets/samples/cmd-review
Command: npx skills add https://github.com/vinhnx/VTCode --skill cmd-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing code changes before committing or merging is time-consuming and easy to skip under pressure. This Skill provides a structured, on-demand review of your current diff or specific files, surfacing bugs, regressions, correctness risks, and missing tests with concrete file and line references.

Core Features & Use Cases

  • Flexible Review Targets: Review the current diff by default, or target specific changes using --last-diff, --target <expr>, --file <path>, or positional file paths.
  • Severity-Ordered Findings: Findings are prioritized by severity with concrete file and line references, keeping the high-level summary brief.
  • Custom Review Styles: Adjust the review output with the --style <style> option to match your team's conventions.
  • Use Case: Before pushing a branch, run /review --last-diff to catch a regression and a missing test case in your staged changes before they reach CI.

Quick Start

Ask the assistant to review the current diff by invoking /review, optionally passing flags like --last-diff or --file src/main.rs to scope the review.

Frequently Asked Questions about cmd-review

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

FAQPage Schema
How do I review my current git diff with a slash command?▼

Invoke /review with no arguments to review the current diff. The skill interprets the raw argument string after the command and defaults to the current diff when the input is empty.

How do I review specific files instead of the whole diff?▼

Pass file paths as positional arguments or use the --file <path> flag, for example /review --file src/main.rs. You can also use --target <expr> or --last-diff to scope the review to particular changes.

What kinds of issues does a code review skill prioritize?▼

It focuses on bugs, regressions, correctness risks, and missing tests before any summary. Findings are ordered by severity and include concrete file and line references.

Can I customize the review output style?▼

Yes, pass the --style <style> option with the /review command to adjust the review output format. The high-level summary is kept brief regardless of the chosen style.

When should I not rely on an automated diff review?▼

Automated review is best for catching correctness risks and regressions, but it does not replace human judgment on architecture, product intent, or domain-specific business logic. Use it as a first-pass check before human review.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
agwacomagwacom

avadbeta-review

Analyze branch diffs to identify defects that tests miss.

Official
Advanced
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
BluMintIncBluMintInc
2

automated-review-addressing

Automate pull request review feedback by updating the PR head branch.

Official
Advanced