Skip to content

clambro/ai-plays-pokemon / .agents/skills/review

review

Verified

Use when the user asks for a code review, PR review, or branch feedback. Reviews the current branch against main.

Code Review

Workflow

  1. Run git branch --show-current to identify the branch. Use main as the base unless the user specifies another branch.
  2. Gather the committed branch changes:
    • git log <base>..HEAD --oneline
    • git diff <base>...HEAD
  3. Read project standards before reviewing:
    • AGENTS.md
    • docs/workflow.md when orchestration changes are involved
  4. Review for correctness and regressions, with particular attention to:
    • async emulator lifecycle and game-state timing
    • ROM/parser assumptions and compatibility with saved fixtures
    • accidental live model calls, telemetry, or other paid external effects
    • Pydantic at I/O boundaries and dataclasses for internal data
    • focused tests and narrow lint/type-check exceptions
  5. Report findings using the output format below.

Output Format

For each issue found:

  1. Assign a number for easy reference
  2. Link the file path and line number
  3. Give severity: 🔴 Problem | 🟡 Suggestion | 💭 Nitpick
  4. Describe the issue
  5. Briefly suggest a fix (if applicable)

Group issues by file. End with a summary of overall assessment. If there are no findings, say so directly and mention any material residual risks or validation gaps.

receiving-code-reviewobra/superpowersUse 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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall