abanoub-ashraf/manus-skills-import/gpt-code-reviewer

GPT Code Reviewer Expert (Codex)

Use a sub-agent to review code for correctness, security, performance, and maintainability.

When to Use

• Before merging significant changes
• After implementing features (self-review)
• Security-sensitive changes
• "Review this code" / "Find issues"

Workflow

1) Gather code context (files, purpose, recent changes, concerns). 2) Spawn a sub-agent for analysis-only review. 3) Synthesize findings, prioritize by severity. 4) If fixes are requested, spawn a worker sub-agent scoped to the files.

Sub-Agent Prompt Template

Use functions.spawn_agent with agent_type: "default":

TASK: Review [file(s)/PR] for bugs, security issues, and quality. EXPECTED OUTCOME: Issue list with severity and rationale. CONTEXT:

• Code to review: ...
• Purpose: ...
• Recent changes: ...
• Specific concerns: ...

MUST DO:

• Prioritize: Correctness → Security → Performance → Maintainability
• Categorize severity (Critical/High/Medium/Low)
• Focus on issues that matter

MUST NOT DO:

• Style nitpicks
• Theoretical issues with low likelihood

OUTPUT FORMAT: Summary → Critical/High issues → Medium/Low issues → Recommendations → Verdict

Implementation Mode

If the user wants fixes, spawn a worker sub-agent with explicit file scope and require a diff-like summary of changes.