system-audit

System integrity validation checks structural file existence and references, relationship graphs map dependencies, and runtime health inspects live artifacts to surface missing files and configuration drift in markdown and JSON reports.

Yes, you can trace upstream and downstream impact for a changed file by running an impact analysis. This maps dependency relationships to guide safe updates and define PR scope without automatically modifying your codebase.

Generate a dependency graph by running the audit script in dependency graph mode. It maps component relationships and outputs structural connections, producing both human-readable markdown and machine-readable JSON artifacts.

No, the system audit does not perform automatic remediation. It provides non-destructive reporting by surfacing missing files and configuration drift in markdown and JSON outputs, leaving all fixes to manual review.

Assess documentation and workflow quality by running a rubric-driven review using the review script. It integrates mechanical checks with qualitative rubric assessment to evaluate docs, commands, and workflow quality in markdown reports.

Yes, you need a project organized under a ~/.claude layout to validate runtime health and component dependencies. The audit scripts rely on this JYH-OS repository structure to inspect live artifacts and build accurate relationship graphs.