Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill to review code changes against Hyperlane monorepo standards.
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.
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.
/inline-pr-comments skill fetches existing reviews/comments so you can avoid duplicating feedback and stay aware of ongoing discussionsWhen reviewing your own changes before committing:
git diff to see changesSecurity issues should use /security-review or /tob-review instead.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.
日本語の概要は準備中です。原文の説明を表示しています。
The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
日本語の概要は準備中です。原文の説明を表示しています。
Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.
日本語の概要は準備中です。原文の説明を表示しています。
Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.
日本語の概要は準備中です。原文の説明を表示しています。