Skip to content

Consensys-Incorporated/ocap-kernel / .claude/skills/code-review

code-review

Verified

How to review code; a pull request, feature branch, local changes etc.

When asked to review code, whether a PR on GitHub or some local changes, provide feedback on:

  • Code quality and best practices
  • Potential bugs or issues
  • Performance considerations
  • Security concerns
  • Test coverage

Use the repository's CLAUDE.md for guidance on style and conventions. For comments, changelog entries, and PR bodies, review against the standard in .claude/skills/prose-pass/SKILL.md — read it as criteria; do not invoke it, since it edits files and a review may have nothing checked out. If you encounter terms that should be added to the glossary, invoke the glossary skill using: Skill tool with skill="glossary" Be constructive and helpful in your feedback.

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: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated 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: 319kUpdated 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: 319kUpdated Claude CodeCodexVerifiedInstall