asset-audit

Audit game assets for naming, size, format, and pipeline compliance.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill asset-audit-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-audit
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/asset-audit
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill asset-audit-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit automates the process of auditing game assets for naming conventions, file size budgets, format standards, and pipeline requirements, helping to identify orphaned assets and missing references.

Core Features & Use Cases

  • Compliance Checking: Automatically checks for naming conventions, file size budgets, format standards, and pipeline requirements.
  • Orphaned Assets Identification: Identifies assets that are not referenced in the code.
  • Missing Assets Identification: Identifies missing assets that are referenced in the code.
  • Report Generation: Generates a comprehensive report outlining all findings and recommendations.

Quick Start

Run the asset-audit skill with the category you want to audit, e.g., asset-audit --category art.

Frequently Asked Questions about asset-audit

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

FAQPage Schema
How do I automate game asset compliance checking for naming conventions and format standards?

Game asset compliance checking is automated by auditing project codebase and asset standards documentation to verify naming conventions, file size budgets, and format standards. The process identifies orphaned and missing assets while generating a comprehensive findings report.

How do I find orphaned game assets that are not referenced in my codebase?

Finding orphaned game assets is handled by scanning the project codebase to identify asset files that lack code references. The audit cross-references existing assets against code dependencies and generates a detailed report listing all unreferenced files.

What is the best way to identify missing assets referenced in game code?

Identifying missing game assets referenced in code is achieved by scanning project scripts for asset references that lack corresponding files. The audit generates a detailed report listing all missing references to resolve pipeline requirements and broken dependencies.

Do I need asset standards documentation to run a game asset audit?

Asset standards documentation is required to run a game asset audit, providing the naming conventions, file size budgets, and format standards for validation. The project codebase is also necessary to cross-reference assets and identify missing or orphaned files.

Can I audit game art assets separately from other categories?

Auditing specific game asset categories like art is supported by passing the target category as an argument. Running the audit with a specified category isolates the compliance checking, format standards validation, and report generation to that specific group.

Why does my game asset audit report show pipeline requirement violations?

Game asset audit reports show pipeline requirement violations when scanned assets fail to meet the format standards or file size budgets defined in the asset standards documentation. The generated report outlines these findings alongside identified orphaned and missing assets.