Inspect before you edit
An existing codebase has conventions and constraints. Inspect the file tree, README, applicable AGENTS.md, and relevant configuration before selecting a change.
What is it?
An existing codebase has conventions and constraints. Inspect the file tree, README, applicable AGENTS.md, and relevant configuration before selecting a change.
Why it matters
Existing behavior and other people’s work need protection.
When to use it
Whenever a project already contains files or user work.
How to do it
- Read the explanation and identify the files or environment involved.
- Use the repository-inspection prompt. Ask for the framework, entry points, existing checks, and files likely affected by a heading correction. Do not edit yet.
- Compare the result with the verification criteria below. Record what worked and what remains unclear.
Worked example
Use the repository-inspection prompt. Ask for the framework, entry points, existing checks, and files likely affected by a heading correction. Do not edit yet.
Try it yourself
Repeat the exercise with your own wording or a second sample. Use the smallest change that demonstrates the idea.
Prompt builderVerify your result
Every important finding points to a file that actually exists. Unknowns are marked as unknowns.
Common mistakes
Trusting an inferred framework without checking configuration. Read the relevant manifest.
How to recover
Stop at the first unexpected result. Preserve your current work, re-check the named file or environment, and repeat only the failing step. Ask for an explanation if the recovery is unclear.
Official references
Product interfaces and access can change. Use the linked official guide for current installation and account requirements.
OpenAI · Quickstart ↗Source review: 2026-09-16