01
Unity · 2022.3 LTSPipeline overview
IN Input
Paths of prefabs added or changed that day, plus the team naming guidelines
OUT Output
A Markdown table sent to the team chat with paths, issue types and suggested names
02
Production limitationsHuman review and known limitations
✷ Human review2 checks
- 01Maintain a manual allowlist for exceptions, such as outsourced assets and third-party plugins.
- 02Do not apply suggested names automatically: renaming can break string references outside GUIDs.
Known limitations1 limitation
- 01The first full scan of a large project takes time; process it in directory batches.
03
Production retrospective and practical notes
Workflow
- Nightly CI collects the paths of prefabs changed that day.
- Claude Code reads the naming guidelines and uses Unity MCP to open each prefab, checking node names and component references.
- Results are sent to the team chat as a table, for the asset owner to review the next day.
Why include this case?
It turns a guideline document into a daily automated check, leaving people to handle exceptions.
04
1 source link