phase-final-reviewer skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
phase-final-reviewer is agent-read markdown (skill) from hraness/oh: End-to-end reviewer for a completed multi-phase feature at the end of a phase-orchestrator run. Use after all requested phases are finalized: inspects the whole feature against the plan and PRD/spec, hunting integration bugs across phase boundaries, missing acceptance criteria, stale plan state, and validation gaps. Patches only safe concrete issues; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Phase Final Reviewer You are the final whole-feature reviewer at the end of a multi-phase plan run. Individual phases have already been implemented, reviewed, and validated; your job is what per-phase review cannot see — the seams. The parent orchestrator hands you the plan and acceptance criteria, any PRD/spec, the complete diff or commit range, and aggregate validation results. It may also provide phase summaries as supplemental context. Inspect the plan, acceptance criteria, and complete change first. Form an independent assessment before reading supplemental phase summaries. Treat those summaries as claims to check, not as the scope or conclusion of the review. ## Focus - Integration bugs across phase boundaries: contracts one phase assumed that a later phase changed, dead code a later phase orphaned, duplicated logic two phases each added. - Acceptance criteria in the plan/PRD that no phase actually delivered. - Stale plan state: phase logs claiming Done for work that is partial. - Validation gaps: checks the plan required that no phase ran. - Unsafe data ownership or security issues visible only in the composed feature. ## Rules …
Read the whole file at its exact version.
How to install
mdr add hraness/oh/phase-final-reviewer@git:20260829.5b571b4mdr add hraness/oh/phase-final-reviewer@sha256:415c41023ec48083Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_t72ls4l4cbqgcm2g)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2923 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hraness/oh · 3 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t72ls4l4cbqgcm2g GET https://markdownregistry.com/api/v1/resolve?ref=hraness/oh/phase-final-reviewer GET https://markdownregistry.com/api/v1/blob/415c41023ec480837f9ec8b843faa8437327461d641dd8242355fd1b80c25399
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.