cold-review

Reviews work artifacts with fresh-context reviewer agents and evidence-based findings.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill cold-review-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cold-review
Source: https://github.com/allemaar/open-skills/tree/main/skills/cold-review
Command: npx skills add https://github.com/allemaar/open-skills --skill cold-review-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that produce work often miss their own defects because they carry too much context, own the implementation, or are biased toward their own choices. This Skill runs an independent review of actual artifacts using fresh reviewer agents, so issues surface that the original agent cannot see. ## Core Features & Use Cases - Fresh-context reviewer agents: Spawns 1-3 reviewers based on work scope (narrow, medium, broad), each assigned a distinct lens such as correctness, security, accessibility, or executability. - Evidence-based findings with self-verification: Every finding requires evidence from source files, and load-bearing findings are re-opened and re-checked at synthesis before the report is returned. - Structured scoring and verdicts: Findings are classified as Critical, Major, Minor, or Interesting, with a 0-100 score mapped to verdict thresholds from clean to blocked. - Use Case: After implementing a multi-file backend change, run a cold review to have independent reviewers check correctness, security, and test coverage against the original objectives before merging. ## Quick Start Ask the agent to cold review the current diff against the original objectives and return a scored report with evidence-backed findings.

Frequently Asked Questions about cold-review

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

FAQPage Schema
How do I get an independent review of my code changes?

Invoke cold review on the diff or files and state the objectives. The skill spawns fresh reviewer agents with distinct lenses such as correctness, security, and tests, then synthesizes their evidence-backed findings into one scored report.

How many reviewers does a cold review use?

One reviewer for narrow work like a single file, two for medium mixed work, and three for broad or high-risk work such as security changes or migrations. More than three reviewers requires explicit user confirmation.

When should I use cold review instead of verify or double-check?

Use cold review for outside critique of concrete work artifacts. Use verify for a formal self-gate on intent, plan, or execution, and double-check when the current agent should re-read and challenge one specific target itself.

What happens if fresh reviewer agents are not available?

The skill performs a degraded single-agent review in the same session and clearly labels the report as degraded, warning that it may miss context-bias issues that fresh reviewers would catch.

Can cold review replace running tests or builds?

No. The skill explicitly states that a high review score does not replace tests, builds, or formal verification. It is a critique layer, not a substitute for executable validation.