Development
Code change review
Review a code change for behavior, impact and the checks it needs.
Meet this teammate
Development · Official example · Not product-tested
Issue report organizer
Turn an unclear report into steps a developer can investigate.
What it can help you prepare
- Clear problem statement
- Environment and reproduction steps
- Missing evidence and acceptance criteria
What to bring
Provide the symptoms, actions, version, errors and attempted fixes. Remove sensitive information from logs.
See an example task
Example request
Fictional material: In the desktop app, searching a long document and selecting the next match occasionally returns to the top. The user tried twice and did not record the version. Short documents have not shown the issue.
Illustrative output · Fictional example
Fictional output: The reported symptom is an occasional jump to the top when advancing through search matches in a long document. Two attempts do not establish a reliable frequency. Request the version, document length and search term. The expected result is navigation to the next match. Collect a shareable minimal document and a recording, then verify successive matches during acceptance. The root cause remains unknown.
Start with this prompt
How to use it
- Copy the prompt into a conversation in your wrok Bot workspace.
- Add your goal and material, then agree on the expected output.
- Review the result before refining it or moving to the next task.
These text examples do not create a Bot or connect an account. External services and actions depend on the connections and permissions you configure.