← ClaudeAtlas

review-strictlisted

Use when: a strict engineering pass is needed — either as a meta-reviewer reading consolidated findings from other reviewers and elevating weak findings, or standalone on a git diff. Covers "strict review", "review --strict", "boss review", "review as boss", or dispatched by review-orchestrator as an optional post-pass after other reviewers complete. NOT for: first-pass review (run domain reviewers first); large refactors outside the diff scope (file separately).
MrCipherSmith/helyx · ★ 1 · Code & Development · score 71
Install: claude install-skill MrCipherSmith/helyx
# Review — Strict (Meta-Reviewer) Strict engineering review pass. This is a **meta-reviewer**: it reads findings from other reviewers (or the raw diff when run standalone) and applies strict engineering judgment. It elevates understated findings, adds architectural commentary, and catches issues that domain reviewers may have let through. Style: direct, no-fluff, engineering-focused. --- ## Workflow ``` review-strict Progress: - [ ] Step 1: Read Job Context (if CONTEXT_PATH provided) - [ ] Step 2: Determine input mode (meta or standalone) - [ ] Step 3: If standalone — determine git scope and collect diff - [ ] Step 4: If meta — ingest findings from other reviewers - [ ] Step 5: Apply strict principles to findings or diff - [ ] Step 6: Elevate understated findings - [ ] Step 7: Add new findings not caught by other reviewers - [ ] Step 8: Check single source of truth violations - [ ] Step 9: Emit enhanced findings + strict commentary ``` --- ## Input Contract | Field | Type | Required | Description | |-------|------|----------|-------------| | `findings` | string | no | Consolidated findings from other reviewers (markdown). When present, operate in meta mode. | | `branch` | string | no | Branch to review. Defaults to current branch. Required in standalone mode. | | `commit_range` | string | no | Explicit range (e.g., `abc123..HEAD`). Overrides merge-base in standalone mode. | | `context_doc` | string | no | Path to job context document (e.g., `<JOBS_ROOT>/<job>/ai/contex