6bnbn/requesting-code-review
兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/requesting-code-review/SKILL.md
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
$ 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%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 25, 2026, 6:56 PM44.5s2 files scanned
SKILL.md
- name:
- requesting-code-review
- description:
- Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Requesting Code Review
Dispatch a review subagent or run the code-review workflow before issues compound.
When to Request Review
Mandatory:
- After each task in subagent-driven development
- After a major feature lands
- Before merge to main
Optional but valuable:
- When stuck and you want a fresh perspective
- Before a risky refactor
- After fixing a subtle bug
How to Request
-
Gather the context to review:
- what changed
- what it was supposed to do
- the relevant diff or commit range
-
Dispatch a review subagent:
- use spawn_agent
- give it the requirements, diff context, and any relevant AGENTS.md guidance
- when reviewing GitHub PRs, include the PR number and gh workflow details if available
-
Act on the findings:
- fix critical issues immediately
- fix important issues before proceeding
- document any deferred minor issues
Review Prompt Inputs
- WHAT_WAS_IMPLEMENTED
- PLAN_OR_REQUIREMENTS
- BASE_SHA
- HEAD_SHA
- DESCRIPTION
Red Flags
- Skipping review because the change feels simple
- Ignoring critical issues
- Proceeding with unfixed important issues
- Accepting review feedback without technical verification
See code-reviewer.md for the reusable review prompt template.
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