Agent skill

Code Review

by XRPLF in XRPLF/XRPL-Standards

Review a pull request in XRPL-Standards. An agent skill from XRPLF/XRPL-Standards.

MITAuto-check passedDevelopment

Install Code Review

skills CLI
$ npx skills add XRPLF/XRPL-Standards --skill code-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install XRPLF/XRPL-Standards code-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/XRPLF/XRPL-Standards.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/code-review .claude/skills/code-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review
GitHub stars
288
Token cost
~825 tokens
SKILL.md length
414 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Review a pull request in XRPL-Standards. An agent skill from XRPLF/XRPL-Standards.

  • Works in 5 steps: Read the PR description and complete diff. → Inspect every changed file and the… → For each changed normative behavior,… → …
  • Any PR in this repository
  • SKILL.md covers Complete the review before…, Follow the repository guidelines, For any changed XLS-*/README.md and Never flag, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Code Review is an agent skill from XRPLF/XRPL-Standards. Review a pull request in XRPL-Standards. Use for any PR in this repository, especially one that changes an XLS-/README.md, the templates, or the validation scripts.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests, Code review and Technical documentation. The repository describes itself as: XLS: XRP(L) community defined Suggestions, Proposals, RFCs / Standards / Drafts & discussions, to be added to the core protocol, used for platform & apps devemopment, etc. The licence is MIT.

When your agent uses it

  • Any PR in this repository
  • Especially one that changes an XLS-/README.md
  • The validation scripts

Example prompts

  • “/code-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read the PR description and complete diff.
  2. Inspect every changed file and the unchanged context needed to validate it.
  3. For each changed normative behavior, check the affected field tables, failure conditions, state changes, invariants, formulas, examples…
  4. Build the complete candidate finding set privately.
  5. Verify each candidate, remove duplicates and previously addressed findings, then submit one review for the current HEAD commit.

What it can do on your machine

Read from SKILL.md and the folder at commit 4dbe8e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review loads about 825 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 414 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~825

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from XRPLF/XRPL-Standards at commit 4dbe8e7, republished under its MIT licence (© XRPLF). 414 words, ~825 tokens.

Download SKILL.mdSave it as .claude/skills/code-review/SKILL.md (or your agent's skills folder).
name
code-review
description
Review a pull request in XRPL-Standards. Use for any PR in this repository, especially one that changes an XLS-*/README.md, the templates, or the validation scripts.

Reviewing a PR in XRPL-Standards

This repository holds prose specifications, not shipping code. A review's job is to find spec defects: ambiguity, internal inconsistency, missing normative detail, unsafe design, or a claim that contradicts the implementation.

Complete the review before commenting

Analyze the complete PR before submitting any comments:

  1. Read the PR description and complete diff.
  2. Inspect every changed file and the unchanged context needed to validate it.
  3. For each changed normative behavior, check the affected field tables, failure conditions, state changes, invariants, formulas, examples, RPCs, parent specification, and amendment patches.
  4. Build the complete candidate finding set privately.
  5. Verify each candidate, remove duplicates and previously addressed findings, then submit one review for the current HEAD commit.

Do not publish findings incrementally as they are discovered. Do not stop after finding the first valid issue.

Follow the repository guidelines

Read .github/copilot-instructions.md — the "Review Guidelines (for AI reviewers)" section is normative for this review. It covers what CI already owns, the process checks, evidence standards, and comment etiquette.

For any changed XLS-*/README.md

Follow .agents/skills/xls-template-conformity/SKILL.md, including its references/beyond-the-template.md. It is the same procedure human contributors run, and it reads templates/ at review time, so it cannot drift from them.

Never flag

Trailing whitespace, line endings, missing EOF newline, markdown or table formatting (prettier owns table alignment — never suggest realigning a table), missing preamble fields, missing required sections, missing Amendment subsections, leftover template placeholders.

Every one of these fails CI on its own. A comment about them is pure noise.

Also suppress spelling, grammar, phrasing, verbosity, naming consistency, field qualification, and optional clarity suggestions unless they create two plausible protocol interpretations or would cause incorrect implementation or client behavior.

Show full SKILL.md (134 more words)Show less

Avoid repeat rounds

Read existing review threads before submitting the review. Do not repeat an issue that was already reported, resolved, answered, or made outdated. Reopen it only if the same defect still exists at the current HEAD, and explain specifically why the earlier response or change did not resolve it.

.ai-review/instructions.md is a committed symlink (git mode 120000). If your view of the tree does not resolve it, it will look absent or look like a one-line file containing a path. Do not report it as missing or malformed.

The .claude/skills/<name>/SKILL.md files are deliberate stubs: name and description frontmatter, which Claude Code needs to discover the skill, plus one line pointing at .agents/skills/<name>/SKILL.md, which holds the procedure. Do not report them as incomplete, and do not propose removing the frontmatter.

© XRPLF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/code-review of XRPLF/XRPL-Standards.

Open the folder on GitHubat commit 4dbe8e7

Compare with similar skills

Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review this skillXRPLF/XRPL-Standards288—~825Automated safety check: PassMIT
Post Draft Reviewagent-substrate/substrate4.5k—~2.8kAutomated safety check: PassApache-2.0
Inline PR Commentshyperlane-xyz/hyperlane-explorer102—~1.1kAutomated safety check: PassCustom licence
PR Review Commentsgiuseppe-trisciuoglio/developer-kit3551 repos~1kAutomated safety check: NotesMIT
Code Reviewtestdouble/han279—~8.7kAutomated safety check: PassMIT
Technical Writingcitypaul/.dotfiles739—~2.5kAutomated safety check: PassMIT

Similar skills

  • Post Draft Review

    agent-substrate/substrate

    Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.

    4.5k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Inline PR Comments

    hyperlane-xyz/hyperlane-explorer

    Post a single consolidated PR review with summary and inline comments.

    102 GitHub stars~1.1k tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • PR Review Comments

    giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.

    355 GitHub starsUsed in 1 repo~1k tokens
    DevelopmentAuto-check: notes
  • Code Review

    testdouble/han

    Run a comprehensive code review on local source files. An agent skill from testdouble/han.

    279 GitHub stars~8.7k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Technical Writing

    citypaul/.dotfiles

    Writing developer-facing prose that can be skimmed first and trusted enough to finish — READMEs, guides, tutorials, reference docs, proposals, PR descriptions, release notes.

    739 GitHub stars~2.5k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

More from XRPLF/XRPL-Standards

  • Spec From Rippled

    XRPLF/XRPL-Standards

    Update an XLS specification to match changes made in rippled.

    288 GitHub stars~764 tokensUpdated 3 days ago
    Auto-check passed
  • Xls Template Conformity

    XRPLF/XRPL-Standards

    Check that an XLS specification conforms to the XRPL-Standards templates.

    288 GitHub stars~859 tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Code Review

What does Code Review do?

Review a pull request in XRPL-Standards. An agent skill from XRPLF/XRPL-Standards. Code Review is an agent skill from XRPLF/XRPL-Standards. Review a pull request in XRPL-Standards.

When should I use Code Review?

Code Review fits situations like: any PR in this repository; especially one that changes an XLS-/README.md; the validation scripts.

How do I install Code Review in Claude Code?

Run `npx skills add XRPLF/XRPL-Standards --skill code-review -a claude-code`. Or copy the skill folder (.github/skills/code-review in XRPLF/XRPL-Standards) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.

How do I install Code Review in Codex?

Run `npx skills add XRPLF/XRPL-Standards --skill code-review -a codex`. Or copy the skill folder (.github/skills/code-review in XRPLF/XRPL-Standards) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.

Can I use Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add XRPLF/XRPL-Standards --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.

What does Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Code Review is instructions for the agent only.

Does Code Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Review use?

Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review use?

About 825 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review?

Skills that share tags, products or a category with Code Review: Post Draft Review (agent-substrate/substrate, 4.5k stars), Inline PR Comments (hyperlane-xyz/hyperlane-explorer, 102 stars), PR Review Comments (giuseppe-trisciuoglio/developer-kit, 355 stars) and Code Review (testdouble/han, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review?

XRPLF (a GitHub organization) maintains it in XRPLF/XRPL-Standards, which has 288 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.

Source: XRPLF/XRPL-Standards on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.