A useful Unity project audit tells you what can safely change next. It is not a competition to find the most warnings or reorganize the most folders. Before a new mechanic or release, establish whether the project can be reproduced, which dependencies matter, and where a small change could break the playable build.
Use the following checklist as a read-first pass. Record evidence and proposed actions separately. This distinction matters when an audit is assisted by a coding agent: identifying a risky asset reference does not automatically authorize deleting or moving the asset.
/01
Reproduce the project before repairing it
Record the exact Editor version, project revision, active build target, package manifest, and starting scene. Ask the maintainer which scene or test route represents the game today. Work from a separate branch or recoverable copy and preserve any existing uncommitted changes. A project that opens only on one developer's machine needs a reproducibility investigation before broad refactoring.
Run the agreed route without changing settings. Save relevant import errors, compilation errors, runtime exceptions, and build failures as distinct findings. Include the action that produced each problem. A vague statement that the console is noisy is hard to act on; a repeatable exception after loading the second level is a clear audit result.
/02
Inspect asset references without breaking identities
Unity uses asset metadata to retain asset identities and import settings. The associated .meta files must travel with their assets. Moving an asset through Unity's Project window handles its matching metadata; moving files outside the Editor requires keeping the pair together. Losing metadata can break existing references. Treat unexplained metadata churn as something to investigate, not routine cleanup.
Inspect the scenes and prefabs on the player route for missing scripts, broken object references, duplicate bootstrap objects, and unexpected overrides. Record the specific object and the user-visible consequence. Do not infer that an asset is unused merely because a text search finds no reference: content may be selected dynamically. Prove a deletion safe in a separate change with a fresh build and a regression pass.
/03
Map ownership of the important runtime state
Identify who owns player input, scene transitions, save data, audio settings, and the game's session state. A small diagram or table is enough. The goal is to find situations where two systems believe they are authoritative, or where an object survives a scene change without an intentional lifecycle.
For an example puzzle game, check what happens when a player restarts during an animation and then returns to the menu. If a score listener or input handler remains active twice, capture that sequence before proposing a fix. An ownership map helps turn a broad complaint about architecture into a bounded task with a clear regression scenario.
/04
Collect evidence from the intended target
Do not use a smooth Editor session as the only performance evidence. Unity's Profiler supports collecting data from a running application on a target device as well as within the Editor. Choose a representative workload, record the capture conditions, and identify the expensive moment before recommending optimization work.
The audit should distinguish a measured bottleneck from a suspicion. For each performance finding, attach the device, build type, scene, action, and capture location. If the intended device is unavailable, say so and leave that check open. A missing measurement is an uncertainty to resolve, not evidence that the release meets its performance goal.
/05
Deliver a short, ranked action list
Group findings by their consequence: cannot build, loses progress, blocks the main action, degrades a supported device, or makes future changes harder. A cosmetic folder inconsistency should not displace a save failure merely because it is easier to fix. Give each recommended action a small scope, an owner, an acceptance check, and a rollback approach.
Close the audit with three lists: confirmed problems, plausible risks needing evidence, and checks that passed. This is more useful than a single reassuring score. AgentGuild's Unity project audit and dependency-audit workflows can structure the investigation, while the project's maintainer retains control over which follow-up changes are approved.
Keep this in mind
Key takeaways
- Reproduce the existing build and player route before changing settings or folders.
- Keep asset metadata intact and prove deletions safe instead of guessing from filenames.
- Rank findings by player and release impact, with an explicit verification step for each fix.
Sources & further reading
Consult the source documentation for the version and platform you are working with.