Review actionable findings
Configurable audit rules, severity filters, search, and documented suppressions.
← All products
Project audits & CI
Release Doctor
Make release checks repeatable.
Run configurable project checks, review findings, and export reports for editor and CI workflows.
Current price, license, version, and checkout details are shown on the marketplace.
Where it fits
Release Doctor
Run a consistent set of checks before a release candidate. Release Doctor audits common project issues, organizes findings by severity, and lets your team document intentional exceptions with suppressions.
Use the editor interface or documented CI entry point. Export reports for review, add custom rules, and compare source-asset size baselines when investigating project changes.
Fit your release workflow
Editor controls, batch-mode CI, explicit exit codes, and custom rule support.
Keep reports usable
HTML, JSON, text, and JUnit export, plus project asset-size baseline comparisons.
Check your project
Know the setup
and the scope.
Current size baselines measure files under Assets, not platform player-build size. An audit does not guarantee a bug-free release, certification, or marketplace approval.
- Editor baseline
- Unity 2022.3 LTS; consult the listing for the supported release
- Requirements
- TextMeshPro for relevant checks; Test Framework only for included tests
- Reports
- HTML, JSON, text, and JUnit
- Audit behavior
- Reports findings without modifying project assets
Start with a small example
Your first integration.
Use the package documentation alongside these steps. Confirm the version you have installed before following a platform-specific workflow.
Read the quick-start guide- Import Assets/UnityReleaseDoctor and read Documentation/QuickStart.md.
- Open Tools > Unity Release Doctor > Open Auditor. Select or create an AuditConfiguration.
- Run a full audit, inspect the findings, and document intentional exceptions with suppressions.
- Export a report. Use Documentation/CIIntegration.md to configure batch-mode execution and its exit codes.
Integration example
Use explicit results in your CI workflow
Illustrative API excerpt. Assign your component references and use the full example in the package documentation.
// CI entry point documented in the package:
Jackmirza.ReleaseDoctor.UnityReleaseDoctorCI.RunAudit
// Exit codes: 0 = no blocking findings,
// 1 = blocking findings, 2 = execution/configuration failure.Before you buy
A few useful details.
Does the audit fix or modify assets?
No. The audit reports findings for you to inspect. Review and apply any project changes through your own workflow.
Does the baseline measure the final player build?
No. The current baseline sums files under Assets. It is a source-project size signal, not a platform build-size measurement.
Does passing guarantee marketplace approval?
No. Marketplace review and project testing cover areas beyond this tool’s checks.
Release Doctor
See the current release.
Review the package details and license on the Unity Asset Store, or ask a setup question first.