caching-and-locking

Diagnose cache misses and locking conflicts in vibe-validate.

3|Updated Oct 16, 2025
One-click install
npx skills add https://github.com/jdutton/vibe-validate --skill caching-and-locking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caching-and-locking
Source: https://github.com/jdutton/vibe-validate/tree/main/docs/skills/caching-and-locking
Command: npx skills add https://github.com/jdutton/vibe-validate --skill caching-and-locking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers diagnose and fix cache misses, unintended cache hits, and concurrency lock conflicts in vibe-validate by explaining the git tree hash caching model, lock scopes, and maintenance utilities like cleanup-temp.

Core Features & Use Cases

  • Understand the git tree hash caching model and how it affects validation performance.
  • Diagnose locking issues across directory and project scopes, adjust concurrencyScope, and use CLI overrides (--no-lock, --no-wait).
  • Practical scenarios: preventing stale caches after edits, resolving parallel validation conflicts, reclaiming temp space with vv cleanup-temp.

Quick Start

Run vv validate in your project and review the tree hash notes to identify whether a cache miss or lock contention is occurring.

Frequently Asked Questions about caching-and-locking

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

FAQPage Schema
How do I resolve locking conflicts during parallel validation?▼

Locking conflicts during parallel validation are diagnosed by adjusting the concurrencyScope setting or applying CLI overrides like --no-lock and --no-wait to bypass directory and project lock contention.

Can I use CLI overrides to bypass project scope locks?▼

Cache invalidation fails when the git tree hash does not match the edited directory state. Running vv validate reviews the tree hash notes to identify whether a cache miss or lock contention is causing the stale cache.

What is the best way to reclaim temp space from failed validation?▼

Yes, you can use the --no-lock and --no-wait CLI overrides to bypass project scope locks. These flags help resolve lock contention when parallel validation conflicts block your directory processing workflow.

Does vibe-validate support concurrency scope adjustments for directory locks?▼

Run the vv cleanup-temp maintenance utility to reclaim temp space left by failed validation. This utility clears temporary files generated during cache misses and lock conflicts across directory and project scopes.

Does vibe-validate support concurrency scope adjustments for directory locks?▼

Yes, vibe-validate supports concurrency scope adjustments for directory locks. You can modify the concurrencyScope setting to manage parallel validation conflicts and prevent lock contention across project scopes.