review_synthesizer

Aggregates Tier 3 audit stamps from REVIEWS.md and LOG.md into a release readiness verdict.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill review-synthesizer-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review_synthesizer
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/review_synthesizer
Command: npx skills add https://github.com/Vimurai/ai-os --skill review-synthesizer-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After multiple audit agents (chaos_monkey, vibe_sentinel, security_engineer, and critic sub-agents) finish their reviews, their pass/fail stamps are scattered across REVIEWS.md and LOG.md with no single authority deciding whether the code is safe to release. This Skill consolidates all of those stamps into one deterministic Release Readiness Report. ## Core Features & Use Cases - Stamp Aggregation: Extracts distributed stamps ([ARCH_PASS], [SEC_PASS], [TESTS_PASS], [ALIGN_PASS]) and aggregated stamps ([SEC_CLEARED], [VIBE_CLEARED], [CHAOS_CLEARED], [PII_CLEARED], [UACS_VERIFIED]) from REVIEWS.md and LOG.md, rejecting any stamp older than 7 days. - CRITIC_STAMP Synthesis: Writes the Tier 3 [CRITIC_STAMP] only after verifying all four distributed pass stamps exist with no newer FAIL stamps. - Severity Gating: Counts P0/P1/P2 findings and blocks release on any unresolved P0 or any P1 without a tracking E-## task in TASKS.md. - Use Case: After a sprint's security, chaos, and architecture audits complete, run this Skill to append a [RELEASE_VERDICT] to REVIEWS.md and stamp [RELEASE_READY] or [RELEASE_BLOCKED] in LOG.md before committing. ## Quick Start Synthesize all Tier 3 audit stamps from REVIEWS.md and LOG.md and write the release readiness verdict for the current E-## task.

Frequently Asked Questions about review_synthesizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide if code is ready to release after multiple audit agents run?▼

Run the review synthesis step after all Tier 3 audits complete. It reads every pass/fail stamp from REVIEWS.md and LOG.md, checks severity findings, and writes a single RELEASE_READY or RELEASE_BLOCKED verdict to LOG.md.

What stamps are required before a release is marked ready?▼

All four distributed stamps (ARCH_PASS, SEC_PASS, TESTS_PASS, ALIGN_PASS) plus the aggregated stamps SEC_CLEARED, VIBE_CLEARED, CHAOS_CLEARED, and UACS_VERIFIED must be present and dated within 7 days. PII_CLEARED is also required when the diff touches user data, auth tokens, or logging.

Why is a release blocked even though all audits passed?▼

A release is blocked if any stamp is older than 7 days, any FAIL stamp exists in the current batch, a P0 finding is unresolved, or a P1 finding lacks a tracking E-## task in TASKS.md. Passing audits alone do not override severity gates.

Who writes the CRITIC_STAMP in a Tier 3 review?▼

For Tier 3 reviews, the review synthesizer writes the CRITIC_STAMP after verifying all four distributed pass stamps exist with no newer FAIL stamps. For Tier 2 reviews, the CRITIC_STAMP is written by the calling review process instead.

What happens when audit stamps are older than 7 days?▼

Stamps older than 7 days are treated as missing, which blocks the release. The relevant audit must be re-run to generate fresh stamps before a RELEASE_READY verdict can be issued.