MichaelVessia/codex-review
modules/programs/agents/shared/skills/codex-review/SKILL.md
Send staged changes to Codex for independent peer review, then evaluate and implement warranted feedback
$ install --global
skillsauthnpx skillsauth add MichaelVessia/nixos-config codex-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 30, 2026, 12:32 PM6.5s1 file scanned
SKILL.md
- name:
- codex-review
- description:
- Send staged changes to Codex for independent peer review, then evaluate and implement warranted feedback
- allowed-tools:
- Bash(git diff:*), Bash(git status:*), Bash(git log:*), Task(codex)
Workflow
Step 1: Send to Codex for review
Use the codex subagent to review staged changes. Pass it the following prompt:
Review the staged git diff as a senior engineer. Provide:
- Critical Issues - bugs, security vulnerabilities, or breaking changes that MUST be fixed.
- Improvements - concrete suggestions for better code quality, performance, or maintainability.
- Nitpicks - minor style or preference items (low priority).
Be specific. Reference exact file paths and lines from the diff. Provide code examples for suggested fixes. Do NOT comment on formatting or whitespace. Do NOT suggest adding comments or docblocks unless something is genuinely confusing. Keep your review concise and actionable.
Step 2: Present the feedback
Display Codex's full review to the user in a clear, formatted way.
Step 3: Evaluate and implement
Read the staged diff yourself (git diff --cached) so you have full context,
then evaluate each piece of Codex's feedback:
- Implement suggestions that are clearly correct improvements (bugs, security issues, genuine code quality wins).
- Ignore anything that is purely stylistic preference, overly cautious, or conflicts with the project's established patterns, conventions, or CLAUDE.md rules.
- Explain briefly which suggestions you're implementing and which you're skipping (and why). You have greater context about this codebase than Codex does.
After making changes, re-stage the modified files.
Related Skills
MichaelVessia/plannotator-visual-explainer
development
VerifiedTrustedCommunity
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
2SKILL.mdUpdated Jun 12, 2026
MichaelVessia/plannotator-setup-goal
development
VerifiedTrustedCommunity
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
2SKILL.mdUpdated Jun 12, 2026
MichaelVessia/plannotator-review
development
VerifiedTrustedCommunity
Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.
2SKILL.mdUpdated Jun 12, 2026
MichaelVessia/plannotator-last
testing
VerifiedTrustedCommunity
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
2SKILL.mdUpdated Jun 12, 2026