What code context should I share?
Include the smallest reproducible example, expected behaviour, actual error, runtime, and relevant dependency versions.
These prompts are strongest when you include the relevant code, error, environment, and constraints. Ask for assumptions and test cases, not just a confident answer. These prompts are built for explaining code, debugging, implementation planning, and technical reviews.
Make the issue easier for someone else to fix.
A guided first read of code that feels opaque.
Think through the contract before you write the code.
A second set of eyes before merge.
Get to a useful query without skipping the safety bits.
Make the next build conversation more concrete.
Improve the code without losing the plot.
Include the smallest reproducible example, expected behaviour, actual error, runtime, and relevant dependency versions.
Remove secrets and personal data, review every change, and run tests or security checks before merging.