Recipes

Issue TemplatePatterns

Structured templates that make bug reports actionable on first read.

Minimal Reproducer

### Summary
[One sentence describing the issue]

### Steps to reproduce
1. Go to '...'
2. Click on '...'
3. Observe '...'

### Expected behavior
[What should happen]

### Actual behavior
[What actually happens — logs, screenshots]

### Environment
- OS: [e.g. Windows 11 23H2]
- Version: [e.g. v2.4.1]
- Hardware: [CPU, RAM, GPU if relevant]

Crash / Hang Report

### Crash description
[What were you doing when it crashed?]

### Reproduction rate
- [ ] Every time
- [ ] Intermittent (~X% of attempts)
- [ ] Only happened once

### Attachments
- Dump file (.dmp)
- Event Viewer log excerpt
- Nimbus debug log (%APPDATA%/Nimbus/logs/)

### System info
- Windows build: [winver output]
- Driver version: [sc query nimbus_drv]
- AV/EDR installed: [list if any]

Feature Request

### Problem statement
[What pain point does this solve?]

### Proposed solution
[How should it work? Be specific about UX]

### Alternatives considered
[What workarounds exist today?]

### Impact
- Who benefits: [e.g. all users / power users / enterprise]
- Urgency: [nice-to-have / important / blocking]

Pro tip: A good issue report eliminates the back-and-forth. Include logs, reproduction steps, and environment details upfront. See the full contributor guide for label conventions and triage SLAs.

← Back to docs