The scenario
This is an unfamiliar checkout; there may be intentional uncommitted changes.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
Read-only boundaries and sourced commands prevent an onboarding explanation from silently changing the project.
A concrete outcome
Produce a concise onboarding map for the current repository so I can safely make my first change.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Inspect instructions, Git status, manifests, entry points and existing checks. Explain the major modules and a small relevant reading order. Do not edit or install anything.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Support every command and framework claim with a repository source; mark setup steps you did not execute.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.