critic-cache

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.

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.

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.

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.

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.

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.