40 lines
1.1 KiB
Markdown
40 lines
1.1 KiB
Markdown
# Examples
|
|
|
|
Use these only to calibrate tone and structure. Do not copy them mechanically.
|
|
|
|
## Example 1: Bug
|
|
|
|
Rough feedback:
|
|
|
|
`Warp loses my selected theme after restart on macOS. I changed it twice and it keeps going back.`
|
|
|
|
Draft shape:
|
|
|
|
- classification: `bug`
|
|
- title: `Theme selection resets after restarting Warp on macOS`
|
|
- missing details: Warp version, macOS version, whether the issue reproduces every restart
|
|
|
|
Key body moves:
|
|
|
|
- turn the complaint into a concrete restart flow
|
|
- state the expected persisted theme behavior
|
|
- mark unknown version details as `Unknown`
|
|
|
|
## Example 2: Feature Request
|
|
|
|
Rough feedback:
|
|
|
|
`The command palette is too hard to scan. I want better grouping for settings-related actions.`
|
|
|
|
Draft shape:
|
|
|
|
- classification: `feature request`
|
|
- title: `Improve Command Palette grouping for settings-related actions`
|
|
- missing details: concrete commands that are hardest to find, screenshots if the user has them
|
|
|
|
Key body moves:
|
|
|
|
- describe the current friction instead of inventing reproduction steps
|
|
- focus the request on the desired workflow and user impact
|
|
- draft immediately unless a specific missing fact blocks clarity
|