Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

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.

Repository
moraine ↗
Licence
Apache-2.0
Last repository change
10.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Original author 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.

How it works

  1. Overview
  2. Review Wave
  3. Triage
  4. Iteration
  5. Final Review Summary
Original SKILL.md headings · 99 lines, 684 words
SKILL.md preview
---
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 skill | Codex | Kiro |
| --- | --- | --- |
| `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.

## 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.
Files in this package (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · eric-tramel/moraine100Apache-2.0
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version 424c91083c86 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100moraine-sandbox-qa
    Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for stack-facing changes.
  • 100moraine-start-work
    Start Moraine repository development work safely. Use when an agent takes on new code, docs, test, CI, packaging, or release work in this repo; when it must create or verify an isolated branch/worktree; when sibling agent collisions are possible; or before editing files for a…
  • 100code-review-and-quality
    Multi-axis code review (correctness, security, performance, design) before merging any change. Use to assess quality; not to refactor (use code-simplification) or hunt complexity only (use over-engineering-review).
  • 100code-review-checklist
    Guide an AI agent through a structured code review — correctness, security, performance, readability, and test coverage — producing a summary with actionable, prioritized feedback. Triggers on pull-request review, diff review, or "review this code" requests.
  • 100review-team
    Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture,…
  • 100code-reviewer
    Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.