path-reference-auditor

To audit file path references, run a three-phase workflow that scans directories, verifies internal boundaries, and reports missing or external links in an inventory.json file. This validates skill-local and plugin-local boundaries for your project.

Validating internal boundaries requires scanning path references to ensure files stay within skill-local or plugin-local limits. The audit generates a reusable inventory.json, supporting repeated checks and automation across your plugins and skills.

Yes, you can automate repeated path reference checks by generating an inventory.json file during the audit report phase. This reusable inventory supports automation and allows you to verify missing or external references across multiple checks.

A symlink boundary check works by scanning file path references to detect external links that cross skill-local or plugin-local limits. The verification phase validates these boundaries and reports any missing references found during the audit.

No dependencies are required to run the path reference audit. You can execute the three-phase workflow directly from the project root to scan, verify, and report on file path references without installing external packages.

Your audit reports missing or external file references because the verification phase enforces skill-local and plugin-local boundaries. It detects any path references that point outside these limits or cannot be found within the scanned directory.