asset-audit

To check game assets for naming violations and size budget issues, scan the asset directory to generate an audit report. This process validates lowercase underscore-delimited naming patterns and verifies file sizes against defined budgets.

The best way to find orphaned assets and missing references is an asset audit that scans code references within the project. This detects files no longer used and locates missing dependencies, outputting a structured compliance report.

An asset pipeline audit verifies format standards by reading asset guidelines and performing file-structure checks on textures, audio, and data. It enforces a standards-driven workflow by validating formats and surfacing violations in a structured report.

Yes, you can use asset-audit to detect unused files before a production build. Running the audit surfaces orphaned assets and standard violations, ensuring your pipeline meets size and format requirements before generating the build.

To scan your asset directory for compliance, provide the directory path and asset guidelines defining your naming, size, and format standards. The audit reads these guidelines to perform file-structure checks and produce the report.