Claude Code can read a project, edit code, and run commands within its configured permissions. A reliable daily workflow starts by tying the request to behavior you can verify. โFix this formโ is broad. โUsers should retain unsaved input when the server rejects an email addressโ describes a result you can test.
Give the session an investigable starting point
Tell Claude where to begin, what you observed, and how to reproduce it. Ask it to find the first point where the state goes wrong before changing files. Supply the exact command you trust for the focused test or ask it to locate the appropriate test entry point. If you have a production error message, remove tokens and private data before pasting it.
Keep the edit and its verification together
For the rejected-email example, a useful task prompt has three checks:
- Reproduce the rejected request with the smallest supported input.
- Preserve typed values while showing the field error clearly.
- Run the relevant form tests and inspect the final diff for unrelated changes.
Have the session report observed results and unresolved questions. Read the diff yourself, especially around validation and recovery, where a fix can silently alter what another caller relies on.
Start a separate task for unrelated work
Keep a dependency upgrade or wider cleanup out of the bug session unless the evidence makes it necessary. A small change with one clear check is easier to review. Save reusable project conventions in the repository's instructions when they apply to other developers and future sessions.
Continue with Oakgen Agent
Open in Oakgen Agent
The prompt is filled in for you. Review it before sending.


