How do I install the Review skill?

Run npx skillmds@latest add adobe/review-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review?

Adobe (@adobe) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review by adobe — Agent Skill

Name: Review
Rating: 4.5 (4 reviews)
Author: Adobe

Review

Review code changes in pull requests or local diffs for S3Mock. Use when asked to review a PR, inspect changes, or provide structured feedback on correctness, conventions, test quality, and documentation. Outputs findings structured as Must fix / Should fix / Nit.

Adobe Updated Sep 22, 2026 142 repo stars

File contents

Code Review Skill

Entry Criteria

Use to review a pull request, a local diff/branch, or to provide structured code-quality feedback.

Before Starting

Read root AGENTS.md and the relevant module AGENTS.md.

Review Scope

Evaluate in this order, citing the specific source rule for each finding:

Correctness — does the code do what it claims (edge cases, error paths)? Check against INVARIANTS.md (XML naming, S3Exception usage, layering).
Convention violations — any INVARIANTS.md violation is Must fix. Also check the "Common Anti-Patterns" tables in docs/SPRING.md and docs/KOTLIN.md for Spring/Kotlin-specific violations (DI style, testing style, var on public API, etc.).
Test quality — coverage of new/changed paths, correct base class and conventions per docs/TESTING.md.
Kotlin idioms — per docs/KOTLIN.md.
Documentation — CHANGELOG.md/README.md/KDoc updated per the document skill's scenario table.

Output Format

Must fix — blocks merge: correctness issues, INVARIANTS.md violations, missing tests
Should fix — idiom/doc improvements; suggest the refactor or lint skill for pure style fixes rather than asking the author to add more code
Nit — optional style suggestions

Execution Steps

Read root + relevant module AGENTS.md.
Evaluate all five categories above, in order.
Produce Must fix / Should fix / Nit findings with file/line references, each citing its source rule.

Completion Criteria

All five categories evaluated
Must fix / Should fix / Nit structure used, each finding cites its source rule
CI gate readiness assessed (ktlint, Checkstyle, tests, Docker build)
CHANGELOG.md check confirmed

Resources

AGENTS.md, INVARIANTS.md
Relevant module AGENTS.md
docs/KOTLIN.md, docs/SPRING.md, docs/TESTING.md

---name: review-3description: Review code changes in pull requests or local diffs for S3Mock. Use when asked to review a PR, inspect changes, or provide structured feedback on correctness, conventions, test quality, and documentation. Outputs findings structured as Must fix / Should fix / Nit.---# Code Review Skill## Entry CriteriaUse to review a pull request, a local diff/branch, or to provide structured code-quality feedback.## Before StartingRead root `AGENTS.md` and the relevant module `AGENTS.md`.## Review ScopeEvaluate in this order, citing the specific source rule for each finding:1. **Correctness** — does the code do what it claims (edge cases, error paths)? Check against `INVARIANTS.md` (XML naming, `S3Exception` usage, layering).2. **Convention violations** — any `INVARIANTS.md` violation is **Must fix**. Also check the "Common Anti-Patterns" tables in `docs/SPRING.md` and `docs/KOTLIN.md` for Spring/Kotlin-specific violations (DI style, testing style, `var` on public API, etc.).3. **Test quality** — coverage of new/changed paths, correct base class and conventions per `docs/TESTING.md`.4. **Kotlin idioms** — per `docs/KOTLIN.md`.5. **Documentation** — `CHANGELOG.md`/`README.md`/KDoc updated per the `document` skill's scenario table.## Output Format- **Must fix** — blocks merge: correctness issues, `INVARIANTS.md` violations, missing tests- **Should fix** — idiom/doc improvements; suggest the `refactor` or `lint` skill for pure style fixes rather than asking the author to add more code- **Nit** — optional style suggestions## Execution Steps1. Read root + relevant module `AGENTS.md`.2. Evaluate all five categories above, in order.3. Produce Must fix / Should fix / Nit findings with file/line references, each citing its source rule.## Completion Criteria- [ ] All five categories evaluated- [ ] Must fix / Should fix / Nit structure used, each finding cites its source rule- [ ] CI gate readiness assessed (ktlint, Checkstyle, tests, Docker build)- [ ] `CHANGELOG.md` check confirmed## Resources- [`AGENTS.md`](../../../AGENTS.md), [`INVARIANTS.md`](../../../INVARIANTS.md)- Relevant module `AGENTS.md`- [`docs/KOTLIN.md`](../../../docs/KOTLIN.md), [`docs/SPRING.md`](../../../docs/SPRING.md), [`docs/TESTING.md`](../../../docs/TESTING.md)

Frequently asked questions