Skill

critic-cache

Checks validity of prior Phase 2.5 critic reviews by hashing plan.json and critic-gates.json against stored hash, skipping redundant runs on cache hit.

Bash

code-quality

automation

Install

npx claudepluginhub closedloop-ai/claude-plugins --plugin code

Tool Access

This skill is limited to using the following tools:

Bash

Preview

Check whether prior critic reviews are still valid, avoiding redundant Sonnet agent launches when the plan hasn't changed since the last critic run.

Supporting Assets

scripts/check_critic_cache.sh

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars83

Parent Repo Forks4

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

Critic Cache

Check whether prior critic reviews are still valid, avoiding redundant Sonnet agent launches when the plan hasn't changed since the last critic run.

When to Use

Activate this skill at the start of Phase 2.5 (Critic Validation), before launching any critic agents. If the cache is fresh, skip the entire critic phase.

Usage

Run the cache check script. The scripts/ directory is relative to this skill's base directory (shown above as "Base directory for this skill"):

bash <base_directory>/scripts/check_critic_cache.sh <WORKDIR>

Interpreting Output

Cache Hit

CRITIC_CACHE_HIT

Action: Skip all critic agent launches. Proceed directly to Phase 2.6 (or Phase 2.7 if no merge is needed). The existing $WORKDIR/reviews/*.review.json files are still valid.

Cache Miss

CRITIC_CACHE_MISS
reason: <why the cache is stale or missing>

Action: Run critics as normal. After all critics complete, stamp the cache:

if [ -f ".claude/settings/critic-gates.json" ]; then
  cat $WORKDIR/plan.json .claude/settings/critic-gates.json | shasum -a 256 > $WORKDIR/reviews/.plan-hash
else
  shasum -a 256 $WORKDIR/plan.json > $WORKDIR/reviews/.plan-hash
fi

How Freshness Works

The script hashes both plan.json and .claude/settings/critic-gates.json (if it exists) into a single combined hash. This ensures:

Plan content changes → cache miss → critics re-run
Critic configuration changes (adding/removing critics) → cache miss → critics re-run
No changes → cache hit → critics skipped

Cache Conditions

Cache hit requires ALL of:

plan.json exists
reviews/ directory exists with at least 1 .review.json file
reviews/.plan-hash exists
Current combined hash matches stored hash