folder-forensic-audit

To audit your repository for technical debt, you run a forensic audit of your project folder structure, documentation, and configuration. This process evaluates folder organization, git hygiene, and CI/CD workflows to identify health issues.

You automate project conformance by applying prescriptive fixes that retrofit your repository to canonical defaults. This automatically establishes standardized CI workflows, ADR templates, and branch protection rules to ensure a consistent developer experience.

A forensic folder structure audit is a comprehensive evaluation of your repository organization, documentation, and configuration against best practices. You need one when a long-running project feels slow or disorganized to identify missing documentation and configuration gaps.

Yes, running a multi-agent project health check requires gitleaks, jq, gh, and pnpm installed in your environment. These dependencies support the forensic audit by enabling secret detection, JSON parsing, GitHub CLI operations, and package management.

Yes, the audit applies prescriptive conformance fixes to automatically retrofit projects with missing documentation and correct configuration gaps. It addresses code health and documentation issues by matching your project to canonical defaults.

Automated repository conformance applies prescriptive fixes based on canonical defaults, which may overwrite custom workflows if not reviewed carefully. While it standardizes developer experience across multi-agent environments, manual validation of complex CI/CD retrofits is recommended.