reviewing-code
Get code review from Codex AI for implementation quality, bug detection, and best practices. Use when asked to review code, check for bugs, find security issues, or get feedback on implementation patterns.
Works with
---
name: reviewing-code
description: Get code review from Codex AI for implementation quality, bug detection, and best practices. Use when asked to review code, check for bugs, find security issues, or get feedback on implementation patterns.
license: MIT
---
# Code Review with Codex
Use `mcp__codex__spawn_agent` for code review.
## When to Use
- Review code quality and patterns
- Find potential bugs or edge cases
- Validate against best practices
- Check for security issues
## Usage
```json
{
"prompt": "Review this code for [quality/bugs/security]: [code or file]"
}
```
## Prompt Examples
- "Review for code quality and Go best practices: [code]"
- "Analyze for security vulnerabilities: [code]"
- "Review for performance issues: [code]"
- "Does this follow idiomatic patterns? [code]"
---
## Gotchas
- **Codex review is non-deterministic** — same code with different invocations gets different priority orderings; pin model version when reproducibility matters.
- **Codex doesn't see staged-but-uncommitted changes by default** — pass them explicitly via `--include-staged` or piped diff.
- **Diff-only review misses cross-file effects** — a renamed function's callsite in another file isn't in the diff, so the rename's blast radius isn't surfaced.
- **Review output ranks by Codex's internal severity heuristic** — not by user-defined priority; re-rank manually for project-specific concerns.
- **Whitespace-only diffs trigger reviews** — pass `--ignore-whitespace` or you get noise.
- **Large diffs (>500 LOC) get summarized**, not reviewed line-by-line — split into focused reviews per file group.More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
