pcc-refresh

Refresh Project Context Cache files with minimal diffs from git changes or explicit scope values.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hollis-labs/volon --skill pcc-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pcc-refresh
Source: https://github.com/hollis-labs/volon/tree/main/plugins/core/skills/pcc-refresh
Command: npx skills add https://github.com/hollis-labs/volon --skill pcc-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill synchronizes the repository's reality with the Project Context Cache (PCC) by applying minimal, targeted updates to the global PCC files so documentation and project context stay accurate without unnecessary rewrites.

Core Features & Use Cases

  • Maps git change signals or an explicit scope to the specific PCC files that must be updated, avoiding broad, noisy edits.
  • Applies minimal diffs: only stale sections are modified, Evidence blocks are appended/updated, and decisions file is append-only to preserve history.
  • Enforces operational invariants and word limits, and can write observability logs when enabled for auditability.
  • Use case: after plugin or docs edits, run this skill to update 00_project, 01_architecture, or 03_workflows with only the rows/blocks affected by the changes.

Quick Start

Run the pcc-refresh skill to update the project's global PCC with minimal diffs for scope all or a specific section.

Frequently Asked Questions about pcc-refresh

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

FAQPage Schema
How do I keep project documentation synchronized with git changes?

To keep project documentation synchronized with git changes, the pcc-refresh skill maps git change-sets to specific Project Context Cache files and applies minimal diffs to update only the affected sections.

What is the best way to update project context cache files without rewriting everything?

Updating project context cache files without broad rewrites is achieved by applying targeted minimal diffs that modify only stale sections, preserving append-only invariants for decisions and respecting word limits.

How do I update the global PCC after modifying project architecture or workflows?

To update the global PCC (.volon/pcc/global) after modifying architecture or workflows, you run the pcc-refresh skill with a specific scope or allow it to detect changes from the git change-set automatically.

Can I track project context cache updates for auditability?

Yes, you can track project context cache updates for auditability by enabling optional observability logs, which record the minimal diffs and targeted file modifications applied during the synchronization process.

Does refreshing the project context cache overwrite previous decisions history?

Refreshing the project context cache does not overwrite decisions history because the skill enforces an append-only invariant for the decisions file, preserving historical records while updating other affected sections.

When should I avoid using automated project context cache synchronization?

You should avoid automated project context cache synchronization when your repository changes require broad structural rewrites rather than targeted section updates, as the skill strictly enforces minimal diffs and word limits.