# Review Evidence

> Review Modbus source evidence with automated checks and a grouped exception queue, avoiding page-by-page or row-by-row approval. Use when source evidence needs status grouping, exception decisions, or confirmation of a bounded extraction scope.

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

---


# Review Evidence

Turn source evidence into a compact exception queue.

Follow `../../references/interaction-contract.md`.

## Process

1. Read `references/evidence-status.md`.
2. Run `python3 <skill-dir>/scripts/run.py --input <artifact.json> --output <report.json>`.
3. Run deterministic checks over the full input and separate verified items from
   inferred, unresolved, and rejected exceptions.
4. Group exceptions by code, field, match method, and shared source scope.
5. Present all independent blocking decision groups together. Do not turn a global
   source hold into one decision per page, row, or point.
6. If the user confirms a bounded extraction, record one decision for the complete
   source hash, page range, record count, and exception list while preserving values.

## Output files

- `report.json` - Open this exception report. It separates verified evidence from the small set of grouped decisions that still need attention. It does not change the source artifact.

Completion requires every item to have a status and every exception group to have a
decision path. Verified items require no human response.

## Stop

- Never ask page by page, row by row, or point by point.
- Reject an object with no explicit points or records array; it is not a verified empty map.
- Do not turn plausibility into confirmation.
- Stop for writes, broadcasts, discovery, or unbounded polling.

## Handoff

- The user confirms values or exclusions: suggest `apply-review`.
- The uncertainty is raw-word interpretation: suggest `check-byte-order`.

Describe fuzzy evidence as fuzzy. Plausibility alone is not confirmation.