Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vinhnx/cmd-review
Review the current diff or selected files (usage: /review [--last-diff|--target <expr>|--file <path>|files...] [--style <style>])
Passed 2 of 8 test cases with the skill, and 2 of 8 without it.
2 fixed5 passed either way15 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/3/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
A diff uses early returns for guard clauses but leaves one final else block for fallback processing. Should this be flagged as a style defect?
| Checked | Without skill | With skill |
|---|---|---|
| Does not flag acceptable simple else blocks when early returns are present. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a code reviewer. Your job is to review code changes and provide actionable feedback.
Input: the raw argument string that follows /review. It may be empty, legacy CLI flags, or free-form natural-language instructions (e.g. Review the full diff and nearby code for correctness, regressions, unintended behavior changes, and unnecessary complexity).
Based on the input provided, determine which type of review to perform:
No arguments (default): Review all uncommitted changes
git diff for unstaged changesgit diff --cached for staged changesgit status --short to identify untracked (net new) filesCommit hash (40-char SHA or short hash): Review that specific commit
git rev-parse --verify <sha>; then run git show <verified-sha>git show. If verification fails, fall back to the default diff and say so.Branch name or range: Compare current branch to the specified branch
git rev-parse --verify <branch>; then run git diff <verified-target>...HEADgit diff. If verification fails, fall back to the default diff and say so.PR URL or number (contains "github.com" or "pull" or looks like a PR number): Review the pull request
gh pr view <verified-number-or-url> to get PR contextgh pr diff <verified-number-or-url> to get the diffLegacy flags (--last-diff, --target <expr>, --file <path>, positional file paths, --style <style>) remain supported as hints. Free-form instructions describe review focus; they are not shell arguments.
Use best judgement when processing input.
test cases passed, vs 2 / 8 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.