How to write a repo-aware prompt before asking a coding assistant to edit files

A repo-aware prompt tells a coding assistant what kind of project it is entering, which behavior matters, and where it should look before editing.

The common mistake is asking for a change as if the repository had no history. “Add login validation” or “fix the table” may be clear to a person who knows the codebase, but a coding assistant needs local context. Without it, the assistant may create a new helper instead of using an existing one, follow the wrong style, or change a shared component without understanding its callers.

A better prompt includes the product surface, relevant files or directories, expected behavior, constraints, and verification command. It can also name what not to change. For example: “This is a React admin screen. Follow existing form validation helpers under src/forms. Do not change API contracts. Verify with the profile form test.”

The prompt should not become a design document. It should give enough orientation that the assistant can inspect the right files and ask better questions. If the codebase has established patterns, naming them directly is often more effective than giving a generic implementation request.

Repo-aware prompting saves time because it reduces unnecessary invention. The assistant can still read the code, but it starts with a map instead of guessing the neighborhood.

How to write a repo-aware prompt before asking a coding assistant to edit files

// COMMENTS

ON THIS PAGE