- A compact packet omits an interface, caller, schema, or test that changes the conclusion
- Ask the model to list missing context, trace dependencies from entry points, and add only the necessary files.
- Large generated or vendored files crowd out relevant code
- Exclude build output, dependencies, lockfile noise, media, and generated artifacts unless the question specifically concerns them.
- The packet includes credentials, customer data, internal keys, or restricted code
- Review the manifest, apply repository ignore rules, redact sensitive values, and use an approved model environment.
- The answer refers to a different commit than the code being changed
- Record the commit and dirty state in the packet, then regenerate after material repository changes.