vc-audit-context

Audit context routing and surface discoverability across Claude and Codex wiring.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-audit-context-withkynam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-audit-context
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-audit-context
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-audit-context-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Audit the project's durable context layer to ensure context routing, surface discoverability, and cross-tool wiring remain stable as the codebase evolves.

Core Features & Use Cases

  • Validate that all durable context documents are discoverable by canonical surfaces and group entrypoints.
  • Validate skill routing references and cross-surface coherence to prevent drift between Claude and Codex surfaces.
  • Use during migrations, restructuring, or split of context surfaces to ensure governance and discoverability are preserved.

Quick Start

Run the audit to verify that process/context files, surfaces, and routing are correctly discoverable and wired.

Frequently Asked Questions about vc-audit-context

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

FAQPage Schema
How do I audit context routing to prevent drift between Claude and Codex surfaces?

You can audit context routing by validating skill routing references and cross-surface coherence to prevent drift between Claude and Codex surfaces. This verifies that durable context documents remain correctly discoverable and wired across evolving codebases.

What is context routing validation and when do I need it for shared skills?

Context routing validation is the process of verifying that durable context documents are discoverable by canonical surfaces and group entrypoints. You need it when your project has evolving process docs and shared skills to ensure routing, discovery, and policy adherence.

How do I validate discovery frontmatter for core context docs during a restructuring?

To validate discovery frontmatter during migrations or restructuring, run the audit to check for the presence of core context docs and enforce frontmatter requirements. This preserves governance and discoverability across split context surfaces.

Can I run a full validator suite to check project context wiring?

Yes, you can optionally run the full validator suite to check project context wiring. This audits the durable context layer to ensure surface discoverability and cross-tool wiring remain stable as the codebase evolves.

Does this context audit work for projects with evolving process documentation?

Yes, the context audit is specifically designed for projects with evolving process and context documentation. It validates that all durable context documents remain discoverable and that governance policies are preserved during changes.