unity-release-readiness
Skill0 starsChanged 4 months agoMITView on GitHub
Audit a Unity project for release, licensing, secrets, settings, builds, crash risks, store requirements, documentation, and source-control cleanliness.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rachitkumarrastogi/unity-mcp-servertheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rachitkumarrastogi/unity-mcp-server★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- meshy-asset-directorSkill
- meshy-unity-importSkill
- unity-animationSkill
- unity-architectureSkill
- unity-audioSkill
- unity-gameplay-systemsSkill
- unity-meshy-studioSkill
- unity-performanceSkill
- unity-scenes-lightingSkill
- unity-shaders-materialsSkill
- unity-testing-ciSkill
- unity-ui-polishSkill
The file
Files
Unity Release Readiness
Audit:
- supported Unity version and package lock
- target platform player settings
- scripting backend and architectures
- scenes in build
- development flags and debug symbols
- secrets and service credentials
- license compatibility of code and assets
- privacy, analytics, permissions, and network disclosures
- save migration and backward compatibility
- crash logging and safe failure behavior
- build reproducibility
- repository size and ignored generated folders
- user-facing credits and third-party notices
Produce blockers, high-risk issues, recommendations, and a go/no-go summary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.