Your first report
in five minutes.

Import the complete package

1. Back up or commit your Unity project.
2. Choose Assets → Import Package → Custom Package.
3. Select indie-release-preflight-1.0.0.unitypackage.
4. Keep the complete Assets/ScopeGarden/ReleasePreflight folder selected and wait for Unity to compile.

Create the sample profile

In the first-run window choose Create sample profile. Reopen the tool at any time through Tools → Scope Garden → Release Preflight.

The sample imports enabled Build Settings scenes and scans project prefabs under Assets.

Review what belongs to this release

• Remove scenes that are not part of the release.
• Use Use enabled Build Settings scenes when Build Settings are your source of truth.
• Narrow prefab folders for large projects—for example Assets/Game/Prefabs.
• Save open scenes before scanning.

Run the preflight

Choose Run preflight. Address failures first, then investigate warnings. A pass is evidence for that specific check and selected scope; it is not a guarantee of a successful build or store approval.

Export the evidence

Choose Export Markdown for a readable report or Export JSON for structured release records and automation. Store it with the build identifier outside Assets unless you intentionally want Unity to import it.

Finish the real release checks

Release Preflight is one part of a release. Run Unity tests, create a real development build, play it on representative hardware, then rerun the preflight after the last relevant change.