Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add hyperlane-xyz/hyperlane-monorepo --skill claude-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Claude Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hyperlane-xyz-claude-review)More formats (shields.io, HTML) on the badges page.
---
name: claude-review
description: Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
---
# Code Review Skill
Use this skill to review code changes against Hyperlane monorepo standards.
## When to Use
- Before committing changes (self-review)
- When asked to review a PR or diff
- To check if changes follow project patterns
## Instructions
Read and apply the guidelines from `REVIEW.md` to review the code changes.
When delegating the review to subagents/teams, pass `REVIEW.md` to each one so every checklist item (e2e tests, casts, allocations, enums) is actually applied — findings the rules already cover should never slip through.
### For PR Reviews
When reviewing a PR, deliver feedback as a **single consolidated GitHub review** using `/inline-pr-comments`. Each run produces a separate review — nothing is overwritten.
1. **Fetch prior reviews first** — the `/inline-pr-comments` skill fetches existing reviews/comments so you can avoid duplicating feedback and stay aware of ongoing discussions
2. **Review body** — Overall assessment, architecture concerns, and issues found outside the diff
3. **Inline comments** — Specific issues on changed lines (attached to the same review)
### For Self-Review
When reviewing your own changes before committing:
1. Run `git diff` to see changes
2. Apply the code review guidelines
3. Fix issues directly rather than commenting
Security issues should use `/claude-security-review` or `/claude-tob-review` instead.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!