critic-cache

Hash plan and critic configuration files to validate review freshness.

102|10|Updated Mar 4, 2026

Search Tags:#automation #developer tools #code review #caching #efficiency

Ready to run

npx skills add https://github.com/closedloop-ai/claude-plugins --skill critic-cache

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: critic-cache
Source: https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/critic-cache
Command: npx skills add https://github.com/closedloop-ai/claude-plugins --skill critic-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents unnecessary re-runs of critic agents by checking if the plan and critic configurations have changed since the last run, saving computational resources and time.

Core Features & Use Cases

Cache Validation: Compares content hashes of plan.json and critic-gates.json against a stored hash.
Conditional Execution: Triggers on entering Phase 2.5, before launching critics, to determine if critics can be skipped.
Use Case: If the codebase plan and critic configurations haven't changed since the last review cycle, this skill will identify that the existing reviews are still valid, allowing the process to bypass the critic phase entirely.

Quick Start

Execute the check_critic_cache.sh script with the current working directory as the argument.

Frequently Asked Questions about critic-cache

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

FAQPage Schema

How do I skip redundant code review agent runs if configurations haven't changed?▼

You can skip redundant code review agent runs by hashing plan and configuration files to compare against stored checksums. If the hashes match, the existing reviews are valid and the critic execution phase is bypassed entirely.

How does file checksum comparison work for caching critic validations?▼

File checksum comparison for caching critic validations works by computing hashes of plan.json and critic-gates.json. The script compares these hashes against previously stored values to determine if the review state is still fresh.

When do I need to validate critic cache freshness in iterative development?▼

You need to validate critic cache freshness during iterative development when entering Phase 2.5. This triggers the cache check before launching agents to ensure configurations haven't changed since the last review cycle.

Do I need bash scripting to automate skipping critic agents?▼

Yes, you need bash scripting to automate skipping critic agents. The execution requires running a shell script that computes and compares file checksums against stored hashes using the current working directory as an argument.

What are the limitations of using file hashing to skip code review phases?▼

The limitation of using file hashing to skip code review phases is that it only detects changes in plan and critic configurations. If source code changes but configurations remain identical, the checksums match and critics may be skipped.

Can I use caching to bypass the critic execution phase if plan.json hasn't changed?▼

Yes, you can use caching to bypass the critic execution phase if plan.json hasn't changed. The validation script checks both plan and gate configurations, skipping agent launches when stored hashes match current file contents.