second-agent-review

Run an independent read-only review of staged code changes by a second agent.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/rapucha/moon-service --skill second-agent-review-rapucha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: second-agent-review
Source: https://github.com/rapucha/moon-service/tree/main/.agents/skills/second-agent-review
Command: npx skills add https://github.com/rapucha/moon-service --skill second-agent-review-rapucha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an implementation pass, a single agent often misses bugs, scope creep, unrequested refactors, or contract drift in its own diff. This Skill adds an independent second-agent review pass that inspects staged or branch changes read-only and reports findings before a task or pull request is finalized. ## Core Features & Use Cases - Independent Diff Review: Delegates review of staged or branch diffs to a separate agent operating in a read-only, code-review stance. - Scope and Policy Checks: Verifies the diff against accepted change categories, review-policy gates, production-use evidence rules, and documentation authority classes. - Structured Findings Output: Returns findings ordered by severity with file and line references, plus a mandatory Diff minimality section separating required from unrequested structural changes. - Use Case: After implementing a public API change, the primary agent stages the diff, invokes this Skill to have a second agent audit it for contract drift, missing tests, and unrequested refactors, then triages each finding as accepted, rejected, or deferred before opening the pull request. ## Quick Start Use $second-agent-review to run an independent read-only review of the current staged changes.

Frequently Asked Questions about second-agent-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a second AI agent to review my code changes?

Stage the intended diff, then invoke this Skill so a separate agent reviews it in a read-only stance against project instructions and policy files. The reviewer reports findings with severity and file references; the primary agent triages and fixes them.

When should I use a second-agent code review?

Use it for changes with meaningful risk: public API or contract changes, scoring and data-transformation logic, provider or privacy boundaries, UI layout work, refactors, and PR-ready branches. Skip it for tiny mechanical edits or single-line fixes.

Can the reviewing agent modify files during the review?

No. The reviewer operates strictly read-only and only reports findings. The primary agent remains responsible for triage, fixes, validation, and the final answer.

What context does the second-agent reviewer need?

Provide project authority files like AGENTS.md, relevant design docs, the staged or branch diff, the accepted change category and scope review, production-use evidence for new extension points, and the validation commands already run with their outcomes.

What happens if the review omits the Diff minimality section?

The review is treated as incomplete. The primary agent asks the same reviewer to finish that section before triage, which completes the existing review rather than starting a new round.