My AI changed twelve files for a small fix and I do not know what to check

A tiny wish can turn into a pile of edits, and the length of a change says little about how much it can hurt. This helper sorts the files your AI touched so the ones that run the whole game come before menus and pictures.

Why this works

In an action game a handful of files decide how every frame behaves. One changed line there touches everything, while a long change in a menu touches a menu. Ranking by kind first and size second points your attention where a slip is costly.

When not to use it

Skip it when the project is tiny enough that you can read every change in a minute, or when your game keeps everything in one file; then the ranking has nothing to separate.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 33 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "My AI changed twelve files for a small fix and I do not know what to check" (read_entry work-act-risky-files-after-ai-edit) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP