review · buiducnhat — Claude Code skill: what it does, how to install
Reviews uncommitted git diffs using full file context and produces structured findings with severity levels and an approval verdict.
MIT 279 installs ★ 48 updated 2026-07-06
npx skills add buiducnhat/cobrew --skill review -a claude-codeWhat review does
The skill inspects current workspace changes using git diff and git diff --cached. Instead of looking only at diff hunks, it reads modified files in full to evaluate surrounding architecture. It also checks docs/SUMMARY.md and project coding standards, running relevant linters or test suites for affected areas when available.
Every issue receives a severity grade from S0 (critical breakages or data loss) down to S3 (minor polish). The final report provides a change summary, prioritized findings tied to file lines, positive observations, and a must-fix checklist. If any S0 or S1 issue is present, the final verdict strictly defaults to Request Changes.
What it helps with
- catch bugs and security flaws in uncommitted git changes
- verify full file context instead of reviewing isolated diff hunks
- generate a prioritized must-fix checklist before committing code
- enforce project coding standards and test coverage on modified files
Example prompts for the agent
- Review current uncommitted git changes and give an approval verdict
- Check staged changes against project code standards and list blocking issues
- Inspect modified files for reliability gaps and generate a review report
How to install review
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill review -a claude-code2Manually: put the files in place
~/.claude/skills/review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review/
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill review -a codex2Manually: put the files in place
.agents/skills/review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill review -a cursor2Manually: put the files in place
.cursor/skills/review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install buiducnhat/cobrew plugins/cobrew/skills/review2Manually: put the files in place
.github/skills/review/SKILL.md1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill review -a gemini-cli2Platform CLI
gemini skills install https://github.com/buiducnhat/cobrew --path plugins/cobrew/skills/reviewManually: put the files in place
.devin/skills/review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review
How to install review in Claude Code?
Run npx skills add buiducnhat/cobrew --skill review -a claude-code in your terminal.
What does the review skill do?
It reviews uncommitted git changes with full file context, classifies issues from S0 to S3, and delivers a structured report with actionable suggestions.
When does the skill issue a Request Changes verdict?
The skill marks the review as Request Changes whenever it identifies at least one blocking issue labeled S0 (critical defect) or S1 (high-priority flaw).
Source text
SKILL.md · MIT
--- name: review description: Review current uncommitted git changes with full file context and produce a structured report with severity levels, actionable fixes, and an approval verdict. license: MIT --- # Review ## Overview Use this skill to review uncommitted changes in the current git workspace. Focus on correctness, safety, maintainability, and alignment with project standards. The review must produce: 1. A concise summary of what changed 2. Prioritized findings with severity labels 3. Actionable fix suggestions 4. A final verdict (`Approve` or `Request Changes`) ## Workflow ### Step 1: Gather Context 1. Inspect current changes: - `git diff` - `git diff --cached` (if staged changes exist) 2. Read the full modified files (not only the diff hunks) to understand surrounding logic and architecture. 3. Load only the project context relevant to the changed files before judging style/patterns: - If `docs/SUMMARY.md` exists, read it first. - Load only task-relevant detail docs. - Prioritize `Code Standard` docs for implementation conventions. - If docs conflict with code or user intent, use the available input/question tool before broad changes. 4. Run relevant quality checks for touched areas (lint/type/tests when practical). ### Step 2: Analyze Changes Evaluate each change across these dimensions: 1. **Correctness** - Does behavior match intended requirements? 2. **Safety & Security** - Are there vulnerabilities, data leaks, auth gaps, or unsafe assumptions? 3. **Reliability** - Are edge cases, null states, retries, and error paths handled? 4. **Style & Consistency** - Does code follow project conventions and established patterns? 5. **Performance** - Any unnecessary expensive operations or regressions? 6. **Testing** - Are critical paths covered with appropriate tests? 7. **Maintainability** - Is the code clear, modular, and easy to evolve? ### Step 3: Classify Findings by Severity Assign one severity per finding using this rubric: - **S0 - Critical** - Production-breaking issue, severe security risk, data corruption/loss, or irreversible side effects - Must be fixed before merge - **S1 - High** - Likely bug, correctness flaw, significant reliability issue, or major missing validation - Should be fixed before merge - **S2 - Medium** - Non-blocking but meaningful issue affecting maintainability, performance, or clarity - Fix recommended soon - **S3 - Low** - Minor improvement, polish, or style-level suggestion - Optional unless team standards require it ### Step 4: Produce Structured Review Report Use the report format below in this exact section order. ## Output Format ### 1) Summary - What changed (2-6 bullets) - Risk profile (low/medium/high) - Areas reviewed (files/modules) ### 2) Findings For each finding, use this template: - **ID**: `R-001` (incrementing) - **Severity**: `S0 | S1 | S2 | S3` - **Category**: `Correctness | Security | Reliability | Style | Performance | Testing | Maintainability` - **Location**: `path/to/file.ext#Lx-Ly` (or function/class name) - **Issue**: Clear statement of the problem - **Why it matters**: User/system impact - **Suggestion**: Concrete fix guidance - **Confidence**: `High | Medium | Low` If no findings exist, explicitly write: **No actionable findings**. ### 3) Positive Notes List good practices observed, such as: - Strong test coverage additions - Clean separation of concerns - Thoughtful error handling - Consistent style and naming ### 4) Must-Fix Checklist Include only `S0` and `S1` findings: - [ ] `R-00X` short fix description - [ ] `R-00Y` short fix description If none, state: **No must-fix items**. ### 5) Verdict Use one of: - **Approve** - No blocking issues (`S0/S1`) remain. - **Request Changes** - One or more blocking issues (`S0/S1`) found. Optionally include: - **Re-review focus**: exact files/areas to re-check after fixes. ## Rules - Be specific and cite exact locations whenever possible. - Do not judge code in isolation; always consider surrounding context. - Prefer actionable suggestions over vague criticism. - Distinguish clearly between blocking and non-blocking feedback. - Avoid speculative claims; if uncertain, lower confidence and explain why. - Align feedback with project documentation and coding standards. ## Review Quality Checklist Before finalizing, confirm: - All modified files were reviewed with context - Each finding has severity, impact, and fix suggestion - Blocking issues are separated into a must-fix checklist - Final verdict matches the finding severities - Feedback is concise, precise, and implementable
© buiducnhat · MIT · buiducnhat/cobrew
Similar skills
All skills for Code review and refactoring →review by other authors comes first.