Prompt examples
These prompts are deliberately explicit about scope and safety. Replace the paths and constraints with the context of your project.
Understand a repository
Section titled “Understand a repository”Inspect this repository without editing files. Summarize the architecture,entry points, test commands, and the five files I should read first. Cite pathsfor every claim.Review a change
Section titled “Review a change”Review the current git diff for correctness, regressions, security issues, andmissing tests. Do not modify files. Report findings by severity and includefile paths and line numbers.Debug a failing test
Section titled “Debug a failing test”Investigate why tests/test_auth.py::test_login_status fails. First inspect therelevant code and test, then run only focused, safe tests. Do not change files.Explain the root cause and propose the smallest fix.Implement a focused feature
Section titled “Implement a focused feature”Implement [feature] in [file/module]. Before editing, inspect the existingpattern and related tests. Keep the change minimal, preserve public behavior,add focused tests, and run the relevant test plus lint. Summarize every changedfile.Refactor safely
Section titled “Refactor safely”Refactor [module] to remove [duplication/problem]. Preserve the public API andbehavior. Do not broaden the scope. Show the plan first, then edit, run focusedtests, and report any remaining risk.Documentation
Section titled “Documentation”Read the implementation and update the documentation so it matches actualbehavior. Do not change code. Add one copy-and-paste example and call out anyprovider, platform, or security limitations.Research or comparison
Section titled “Research or comparison”Compare [options] for this project using only the available documentation andrepository evidence. Separate confirmed facts from recommendations, listtrade-offs, and end with a short recommendation.Work with an image
Section titled “Work with an image”Inspect the attached screenshot. Describe the visible error, identify likelyUI elements involved, and propose a debugging checklist. Do not edit files orclaim certainty where the screenshot is ambiguous.Small release checklist
Section titled “Small release checklist”Prepare a release-readiness report without changing files. Check the workingtree, version consistency, documentation links, tests, lint, and git diff.Separate blocking issues from follow-ups and include the exact verificationcommands.Prompting tips
Section titled “Prompting tips”- State whether the agent may edit files, run commands, or only inspect.
- Name the expected files, tests, and acceptance criteria.
- Ask for a plan before a multi-file change.
- Prefer focused tasks over “fix everything”.
- Ask for evidence: paths, test names, and command output summaries.
- Do not include secrets, access tokens, or private customer data.