agentleFS
Sign inStart free
hyperlane-xyzhyperlane-xyz/hyperlane-monorepo/.agents/skills/code-review/SKILL.md

code-review

Skill77 starsChanged 20 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to review code changes against Hyperlane monorepo standards.

    line 10
  2. Distinctive:

    Before committing changes (self-review)

    line 14
  3. Distinctive:

    When asked to review a PR or diff

    line 15
  4. Very specific:

    Read and apply the guidelines from REVIEW.md to review the code changes.

    line 20
  5. Very specific:

    When delegating the review to subagents/teams, pass REVIEW.md to each one so every checklist item (e2e tests, casts, allocations, enums) is …

    line 22
  6. Very specific:

    When reviewing a PR, deliver feedback as a single consolidated GitHub review using /inline-pr-comments.

    line 26
  7. Distinctive:

    When reviewing your own changes before committing:

    line 34
  8. Distinctive:

    Run git diff to see changes

    line 36

“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 /security-review or /tob-review instead.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free