Code Review

Review code for correctness, security, maintainability, and style. Use when reviewing pull requests, examining code changes, or performing code review. Use when this capability is needed.

tomevault-io Updated

File contents

Code Review

Checklist

  • Correctness: Logic correct, edge cases handled
  • Security: No obvious vulnerabilities (injection, auth bypass)
  • Maintainability: Readable, no unnecessary complexity
  • Tests: Adequate coverage for changes
  • Style: Matches project conventions

Severity Levels

  • Critical: Must fix (bug, security issue)
  • Suggestion: Should improve (readability, pattern)
  • Nice to have: Optional enhancement

Feedback Format

  • Be specific: point to the code
  • Explain why: "Consider X because Y"
  • Suggest fix when possible
  • Acknowledge good patterns

What to Avoid

  • Nitpicking style (use linter)
  • Vague feedback ("this could be better")
  • Blocking on non-blocking issues

Source: iamjcabalejo/payoys-cursor-sub-agents — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/iamjcabalejo--payoys-cursor-sub-agents--code-review commit 68ab49a432

Frequently asked questions

npx skillmds@latest add tomevault-io/code-review-308