6bnbn/code-review
兼容codex@cursor一键安装技能/cursor一键安装技能/纯手动安装/skills/code-review/SKILL.md
Use when the user asks for a code review of local files, a workspace, a branch diff, or a pull request. Focus on real bugs, regressions, accessibility issues, and misleading behavior, with findings ordered by severity.
$ install --global
skillsauthnpx skillsauth add 6bnbn/flowpilot code-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: May 2, 2026, 10:34 AM150.1s1 file scanned
SKILL.md
- name:
- code-review
- description:
- Use when the user asks for a code review of local files, a workspace, a branch diff, or a pull request. Focus on real bugs, regressions, accessibility issues, and misleading behavior, with findings ordered by severity.
Code Review
Goal
Find real issues first. Prioritize correctness, regressions, accessibility, security, and misleading UX over style commentary.
Scope Selection
- If the user names files or paths, review those first.
- If there are local changes, review the changed files and relevant nearby context.
- If a branch diff or pull request is provided, review the diff and then read surrounding code only where needed.
- If scope is unclear, ask what should be reviewed instead of scanning the entire repo blindly.
Review Workflow
- Understand the intent of the change.
- Inspect the relevant files, diffs, and nearby code paths.
- Look for real execution risks: wrong logic, missing edge cases, state bugs, API misuse, broken UX flows, accessibility problems, and misleading UI behavior.
- Validate each suspected issue against the actual code before reporting it.
- Report only high-signal findings.
Output Format
- List findings first, ordered by severity.
- For each finding include:
- severity
- file or scope
- concise explanation
- suggested fix when clear
- If no findings are found, say so explicitly and mention residual risks or testing gaps.
Avoid
- Praise-first reviews that bury the real issues.
- Pure formatting or style nitpicks unless the user asked for them.
- Reporting speculative issues without evidence.
- Treating missing tests as the main finding unless the risk is concrete.
Optional PR Workflow
If GitHub or git context is available, include PR or diff context. If not, do a local review and clearly state what information was unavailable.
Related Skills
6bnbn/writing-skills
testing
VerifiedTrustedCommunity
Use when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.
128SKILL.mdUpdated May 2, 2026
6bnbn/writing-plans
development
VerifiedTrustedCommunity
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
128SKILL.mdUpdated May 2, 2026
6bnbn/verification-before-completion
development
VerifiedTrustedCommunity
Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.
128SKILL.mdUpdated May 2, 2026
6bnbn/using-superpowers
testing
VerifiedTrustedCommunity
Use when starting a task in Cursor and deciding whether to apply one of the companion skills in this pack before exploring, planning, editing, or reviewing.
128SKILL.mdUpdated May 2, 2026