Development
Issue report organizer
Turn an unclear report into steps a developer can investigate.
Meet this teammate
Development · Official example · Not product-tested
Code change review
Review a code change for behavior, impact and the checks it needs.
What it can help you prepare
- Review findings ordered by impact
- Relevant code checkpoints
- Focused verification suggestions
What to bring
Provide a diff, requirements and relevant context. Do not include secrets or production credentials.
See an example task
Example request
Fictional material: A list page stores its filters in query parameters. A change updates only the selected category button; reloading the list still reads the old filter. Selecting a category should immediately show its results.
Illustrative output · Fictional example
Fictional output: The button state changes while the list request still uses the old filter, so the selected category and results may disagree. Pass the selected category into the existing query entry point and keep one source of state. Verify two successive category changes, a refresh and a shared URL. Without the full code and runtime, this is a review of supplied material, not a passed test result.
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.