New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Multi-Persona Code Review

by eric-tramel in eric-tramel/moraine

Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes.

Apache-2.0Auto-check passedDevelopment

Install Multi-Persona Code Review

skills CLI
$ npx skills add eric-tramel/moraine --skill code-review -a claude-code

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

GitHub CLI
$ gh skill install eric-tramel/moraine 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/eric-tramel/moraine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/moraine-dev/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
117
Token cost
~1.3k tokens
SKILL.md length
497 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes.

  • Works in 5 steps: Reuse the existing subagent sessions… → Message only the reviewers whose… → Include a concise update with the… → …
  • Reviewing a Moraine pull request from every review perspective at once
  • SKILL.md covers Overview, Review Wave, Triage and Iteration, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Invoking this skill counts as an explicit request for delegated multi-agent review, so the agent does not ask permission to spawn reviewers and does not collapse the personas into one local review. If subagent tooling is unavailable, the review is reported as blocked.

One reviewer subagent is launched for each persona: elegance, idiom, correctness, completeness, security review, YAGNI and scope. Each gets the same raw review packet, made of the PR description, cited issue or objective, relevant diff, changed files, validation results and your constraints, and never the agent's own intended fix or private diagnosis. Invocation forms differ between Codex and Kiro, and the agent keeps a mapping of persona to subagent session.

The agent then merges the feedback, applies accepted fixes and follows up only with the reviewer sessions that need another look. Each reviewer is told to focus only on its own facet, return findings first with severity and file and line references where available, and say so if there are none while noting residual risk.

When your agent uses it

  • Reviewing a Moraine pull request from every review perspective at once
  • Iterating on review feedback after fixes were applied
  • Running reviewer subagents over a local change before opening a PR

Example prompts

  • “Run the full multi-persona code review on this PR and apply the fixes you accept.”
  • “Review my local changes with all seven reviewer personas and summarize the findings.”
  • “Send the correctness and security reviewers another look after my fixes.”

Requirements

  • An agent harness that can launch subagents, such as Codex or Kiro

Workflow steps

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

  1. Reuse the existing subagent sessions from the first wave.
  2. Message only the reviewers whose findings were fixed, rejected with uncertainty, or marked needs-clarification.
  3. Include a concise update with the specific diff or reasoning relevant to that reviewer.
  4. Do not message reviewers whose facet was unaffected.
  5. Do not launch replacement reviewers unless the original session is unavailable and that reviewer is necessary to complete the task.

What it can do on your machine

Read from SKILL.md and the folder at commit 2fb4aec. 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

Multi-Persona Code Review loads about 1.3k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 497 words of instructions outside code blocks.

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

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 eric-tramel/moraine at commit 2fb4aec, republished under its Apache-2.0 licence (© eric-tramel). 497 words, ~1,299 tokens.

Download SKILL.mdSave it as .claude/skills/code-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
code-review
description
Coordinate a delegated full multi-persona code review for a Moraine PR or local change. Use when asked to review a PR, run review agents, get code review feedback, or iterate on review feedback using all CodeReview personas: elegance, idiom, correctness, completeness, security, YAGNI, and scope. Invoking this skill is an explicit request to launch reviewer subagents.

Code Review

Overview

Use this skill to run one coordinated review wave across all focused review personas, merge their feedback, apply accepted fixes, and follow up only with the reviewer sessions that need another look.

Invoking this skill is an explicit user request for delegated multi-agent review. Do not ask for separate permission to spawn reviewer subagents, and do not collapse the personas into a single local review. If subagent tooling is unavailable, report the delegated review as blocked.

Review Wave

Launch exactly one delegated subagent for each focused skill. Use the invocation form native to the current harness:

Persona skillCodexKiro
code-review-elegance$moraine-dev:code-review-elegance/code-review-elegance
code-review-idomatic$moraine-dev:code-review-idomatic/code-review-idomatic
code-review-correctness$moraine-dev:code-review-correctness/code-review-correctness
code-review-completeness$moraine-dev:code-review-completeness/code-review-completeness
code-review-security-review$moraine-dev:code-review-security-review/code-review-security-review
code-review-yagni$moraine-dev:code-review-yagni/code-review-yagni
code-review-scope$moraine-dev:code-review-scope/code-review-scope

Give each reviewer the same raw review packet: PR description, cited issue or objective, relevant diff, changed files, validation results, and any constraints from the user. Do not include your intended fix or your private diagnosis in the prompt.

In Codex, use prompts shaped like:

text
Use $moraine-dev:code-review-correctness to review this PR. Focus only on your persona's facet.
Return findings first, with severity and file/line references when available.
If there are no findings, say so and mention residual risk.

Review packet:
<PR title/body, objective, diff summary, validation, relevant files>

In Kiro, simply name the skill:

text
Use the code-review-correctness skill to review this PR. Focus only on that persona's facet.
Return findings first, with severity and file/line references when available.
If there are no findings, say so and mention residual risk.

Review packet:
<PR title/body, objective, diff summary, validation, relevant files>

Keep a mapping of persona to subagent session id. This mapping is part of the work product until review follow-up is complete.

If the current harness has no callable subagent mechanism, stop before reviewing and report that the required delegated review wave is blocked by missing tooling. Do not silently substitute a manual single-agent review for this skill.

Triage

Wait for the first review wave to finish, then combine findings into one triage list.

For each finding, decide:

  • accept: implement or document the fix.
  • reject: explain why the finding is not applicable.
  • defer: record as follow-up because it is valid but outside this PR.
  • needs-clarification: ask the same reviewer session a targeted question.

Treat CodeReviewScope as the guardrail for the whole review. If another persona asks for broader behavior, generalized architecture, extra cleanup, or unrelated hardening, compare that request against the scope review before accepting it. Prefer the scope review when the broader request would cross lanes or expand the PR beyond its objective.

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

Iteration

Apply accepted fixes in the current workspace. Do not start a new wave of review agents after making changes.

If follow-up review is requested or needed:

  1. Reuse the existing subagent sessions from the first wave.
  2. Message only the reviewers whose findings were fixed, rejected with uncertainty, or marked needs-clarification.
  3. Include a concise update with the specific diff or reasoning relevant to that reviewer.
  4. Do not message reviewers whose facet was unaffected.
  5. Do not launch replacement reviewers unless the original session is unavailable and that reviewer is necessary to complete the task.

Example follow-up prompt:

text
Follow-up on your CodeReviewScope finding about the monitor restyle.
I removed the unrelated CSS changes and kept only the MCP filtering docs update.
Please re-check only that scope concern against this updated diff:
<small diff or file references>

Final Review Summary

Report the review outcome with:

  • Persona coverage: which reviewer sessions ran.
  • Accepted findings and changes made.
  • Rejected or deferred findings with short rationale.
  • Scope guardrail decisions, especially where broader suggestions were not taken.
  • Follow-up sessions messaged, if any.
  • Validation rerun after fixes.

If no actionable findings remain, say that clearly and identify any residual risk.

© eric-tramel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/moraine-dev/skills/code-review of eric-tramel/moraine.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 2fb4aec

Compare with similar skills

Multi-Persona 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.

Multi-Persona Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi-Persona Code Review this skilleric-tramel/moraine117—~1.3kAutomated safety check: PassApache-2.0
Multi-Model Adversarial Reviewcursor/plugins10k8 repos~1.3kAutomated safety check: PassNone
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Adversarial Codebase Auditben-manes/caffeine18k—~1.9kAutomated safety check: NotesApache-2.0
Subagent-Driven DevelopmentHoangNguyen0403/agent-skills-standard570—~852Automated safety check: PassMIT
Clawteamwin4r/ClawTeam-OpenClaw1.5k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Multi-Model Adversarial Review

    cursor/plugins

    Official

    Runs one read-only reviewer subagent per configured model against a diff to challenge a change, then synthesizes a single verdict without applying any fixes.

    10k GitHub starsUsed in 8 repos~1.3k tokens
    DevelopmentAuto-check passed

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Adversarial Codebase Audit

    ben-manes/caffeine

    Runs a hostile review of the Caffeine Java caching library with parallel subagents that get no design docs, then challenges and consolidates their findings.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    570 GitHub stars~852 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Clawteam

    win4r/ClawTeam-OpenClaw

    Multi-agent swarm orchestration. An agent skill from win4r/ClawTeam-OpenClaw.

    1.5k GitHub stars~3.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from eric-tramel/moraine

All 19 skills in this repo

  • Moraine Release Publisher

    eric-tramel/moraine

    Cuts and publishes a Moraine release end to end: version bump PR, tag, GitHub release notes, workflow check and PyPI package verification.

    117 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Moraine Release Notes

    eric-tramel/moraine

    Rewrites a moraine GitHub release body into a usage-focused format with install block, what's new, platform table, upgrade notes and one deduplicated changelog.

    117 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed

  • Elegance-Focused Code Review

    eric-tramel/moraine

    Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems.

    117 GitHub stars~473 tokensUpdated 2 days ago
    Auto-check passed

  • Idiomatic Code Review

    eric-tramel/moraine

    Reviews a pull request for idiomatic implementation: use of the language, standard library, ecosystem conventions and the repository's own patterns.

    117 GitHub stars~469 tokensUpdated 2 days ago
    Auto-check passed

  • Code Review Security Review

    eric-tramel/moraine

    Review a PR through the CodeReviewSecurityReview persona. An agent skill from eric-tramel/moraine.

    117 GitHub stars~497 tokensUpdated 2 days ago
    Auto-check passed

  • Crystallize

    eric-tramel/moraine

    Turn a rough feature, bug, refactor, architecture, documentation, or operations idea into a ready-to-implement local plan file.

    117 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Multi-Persona Code Review

What does Multi-Persona Code Review do?

Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes. Invoking this skill counts as an explicit request for delegated multi-agent review, so the agent does not ask permission to spawn reviewers and does not collapse the personas into one local review. If subagent tooling is unavailable, the review is reported as blocked.

When should I use Multi-Persona Code Review?

Multi-Persona Code Review fits situations like: reviewing a Moraine pull request from every review perspective at once; iterating on review feedback after fixes were applied; running reviewer subagents over a local change before opening a PR.

How do I install Multi-Persona Code Review in Claude Code?

Run `npx skills add eric-tramel/moraine --skill code-review -a claude-code`. Or copy the skill folder (plugins/moraine-dev/skills/code-review in eric-tramel/moraine) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.

How do I install Multi-Persona Code Review in Codex?

Run `npx skills add eric-tramel/moraine --skill code-review -a codex`. Or copy the skill folder (plugins/moraine-dev/skills/code-review in eric-tramel/moraine) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.

Can I use Multi-Persona 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 eric-tramel/moraine --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 Multi-Persona Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Multi-Persona Code Review is instructions for the agent only. Our summary lists: An agent harness that can launch subagents, such as Codex or Kiro.

Does Multi-Persona 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 Multi-Persona 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 Multi-Persona Code Review use?

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

How many tokens does Multi-Persona Code Review use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Multi-Persona Code Review?

Skills that share tags, products or a category with Multi-Persona Code Review: Multi-Model Adversarial Review (cursor/plugins, 10k stars), O2 Review Loop (openobserve/openobserve, 22k stars), Adversarial Codebase Audit (ben-manes/caffeine, 18k stars) and Subagent-Driven Development (HoangNguyen0403/agent-skills-standard, 570 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi-Persona Code Review?

eric-tramel (a GitHub user) maintains it in eric-tramel/moraine, which has 117 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 5, 2026.

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