906 B
906 B
name, description, type, originSessionId
| name | description | type | originSessionId |
|---|---|---|---|
| Don't build after every code change | Don't automatically run build.py after every edit; wait for the user to ask for a build | feedback | a2780d4f-894b-402a-8101-324052832606 |
Do not run build.py (or any build command) after every code change. The user will explicitly ask for a build when they want one.
Why: The user is iterating quickly and doesn't want to wait for builds between every small edit. Builds take ~10s and add noise to the conversation. The user will batch up several changes and ask for a build when they want to verify.
How to apply:
- Make code edits and report them. Stop there.
- Only run
build.py c++when the user explicitly asks ("build please", "build", "verify it compiles", etc.). - Don't proactively build after a rename, refactor, or other "obviously needs verification" change. Trust the user to ask if they want it.