6bnbn/requesting-code-review
兼容codex@cursor一键安装技能/cursor一键安装技能/纯手动安装/skills/requesting-code-review/SKILL.md
Use after completing meaningful implementation work in Cursor and before merging or declaring the change ready, so the result gets a focused review for bugs, regressions, and maintainability risks.
$ install --global
skillsauthnpx skillsauth add 6bnbn/flowpilot requesting-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 AM3.0s1 file scanned
SKILL.md
- name:
- requesting-code-review
- description:
- Use after completing meaningful implementation work in Cursor and before merging or declaring the change ready, so the result gets a focused review for bugs, regressions, and maintainability risks.
Requesting Code Review
Goal
Ask for a focused review at the right time, with the right scope.
When To Use
- After finishing a substantial feature or bug fix
- Before merging or creating a pull request
- After a risky refactor
- When local changes affect behavior, API contracts, or UI flows
How To Ask
Provide:
- what changed
- which files or diff should be reviewed
- what behavior matters most
- any specific concerns such as accessibility, regressions, or edge cases
Good Prompt Shape
- "Review the changed files for real bugs and regressions."
- "Review this branch diff and focus on API behavior and edge cases."
- "Review this UI change for accessibility and misleading interaction states."
After Review
- Fix high-severity issues first.
- Clarify or push back when a suggestion does not fit the codebase.
- Re-run relevant verification before declaring the work ready.
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