Use File Pointers Instead of Dumping the Repository

The decision behind the technique

Uploading or pasting an entire repository repeats irrelevant context and can hide the actual contract. A small set of anchors makes the investigation faster and easier to audit.

Precise starting points reduce noise while preserving Codex’s ability to follow the real call chain.

A practical step-by-step workflow

Use this sequence as a default, then tighten or expand it only when the evidence changes.

• Name the failing test or user route
• Point to the entry file and interface definition
• Include the exact error text
• Ask Codex to justify every additional file it opens

Failure boundary and finish line

Do not omit generated schemas, configuration or shared types when they define the behavior.

Finish when the next action, owner, evidence and stop condition are all explicit.