# Review Sweep

> Use when findings from local review, PR feedback, or CI need verification, triage, accepted fixes, and clear parent-owned defers.

- Skill: `sreejithraman/review-sweep` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add sreejithraman/review-sweep`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sreejithraman/review-sweep/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sreejithraman (https://skillmd.com/u/sreejithraman)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sreejithraman/review-sweep

---


# Review Sweep

Review sweep turns raw technical findings into verified decisions, accepted fixes, and parent-owned defers.

Source wrappers fetch input and handle external side effects such as replies, remote thread resolution, commits, pushes, and issue creation. This skill owns normalization, verification, classification, local fixes, and the return summary.

## Steps

1. Normalize raw input using `references/finding-schema.md`.

   Map each raw item into a finding. Merge duplicates that point to the same underlying issue. Record raw input without a technical claim as source noise. Finish this step when every raw item is a finding, a duplicate, or source noise.

2. Verify each finding.

   Check findings against actual code and project context before trusting them. Treat review wording as input, not truth.

   For each finding, inspect the referenced code, nearby ownership boundary, changed behavior, tests or build impact, public contracts, security or data-loss risk, and local conventions. Decide whether the claim is true, duplicate, pre-existing, already handled, contradicted by code, or more churn than clarity. Finish this step when every finding has evidence and a verified claim state.

3. Classify each finding using `references/classification.md`.

   Assign exactly one class. Only `Must-fix` and `Worth-fixing` are accepted findings. Finish this step when every verified finding has one class and a reason.

4. Fix accepted findings.

   Preserve intended behavior and public contracts. Behavior changes require user approval. Run focused verification after meaningful fixes. Finish this step when every accepted finding is fixed or has an explicit blocker.

5. Return grouped results using `references/return-format.md`.

   Include changed files, verification results, blockers, and every parent-owned defer.