codewithbehnam/review
skills/review/SKILL.md
Review the current diff for bugs, security issues, logic errors, and style problems. Use when the user asks to review changes, check a diff, audit recent edits, or says "review my code", "check this diff", or "look for issues".
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add codewithbehnam/cc-docs reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 3:21 AM59.6s1 file scanned
SKILL.md
- name:
- review
- description:
- >
- context:
- fork
- agent:
- Explore
- allowed-tools:
- Read, Grep, Glob, Bash(git *)
Context
- Current diff: !
git diff HEAD - Staged changes: !
git diff --cached - Changed files: !
git diff HEAD --name-only - Recent commits: !
git log --oneline -10
Task
Review all changes shown in the diff above. For each file, analyze:
- Correctness: logic errors, off-by-one errors, incorrect conditionals, unhandled edge cases
- Security: injection vulnerabilities, missing input validation, hardcoded secrets, insecure defaults, OWASP top-10 issues relevant to the change
- Error handling: uncaught exceptions, missing null/undefined checks, swallowed errors
- Performance: N+1 queries, unnecessary loops, missing indexes hinted by the change
- Style and maintainability: overly complex functions, missing tests for new logic, unclear variable names
- Read any files that are partially shown in the diff to understand full context before commenting
Output Format
Produce a structured review with these sections:
Summary
One-paragraph overview of what the changes do.
Issues Found
For each issue, include:
- Severity: Critical / High / Medium / Low
- File and line:
path/to/file.ts:42 - Description: what the problem is and why it matters
- Suggestion: specific fix or approach
Positive Observations
Note any particularly good patterns, clean code, or well-handled edge cases.
Verdict
One of: "Approved", "Approved with suggestions", or "Changes requested" - with a one-line rationale.
If the diff is empty, report "No changes found to review."
Related Skills
codewithbehnam/steer
tools
VerifiedTrustedCommunity
macOS GUI automation CLI. Use steer to see the screen, click elements, type text, send hotkeys, scroll, drag, manage windows and apps, run OCR on Electron apps, and wait for UI conditions.
1SKILL.mdUpdated Apr 18, 2026
codewithbehnam/ship
testing
VerifiedTrustedCommunity
Ship workflow: merge main, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
1SKILL.mdUpdated Apr 18, 2026
codewithbehnam/setup-browser-cookies
testing
VerifiedTrustedCommunity
Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.
1SKILL.mdUpdated Apr 18, 2026
codewithbehnam/retro
development
VerifiedTrustedCommunity
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
1SKILL.mdUpdated Apr 18, 2026