Write a bug report
Turns an error message or complaint into a clear bug report with steps to reproduce.
A bug report that developers can start on right away.
When to use
- When a bug was reported but described vaguely.
- Before you open an issue on GitHub or in your ticket system.
Needs
- The error message, log excerpt, screenshot or the user’s description.
- Optional: version, device, browser, time.
Steps
- Sum up the bug in a title of no more than ten words.
- Describe the expected and the actual behaviour.
- Write numbered steps to reproduce it.
- State the environment (version, device, browser) and attach the key line from the log.
- Rate the severity and explain it in one sentence.
Check before answering
- Missing details are listed as questions for the reporter.
- Personal data, tokens and passwords are removed from logs.
- One bug per report.
Output
A bug report with “Title”, “Expected”, “Actual”, “Steps”, “Environment”, “Log” and “Severity”.
Limits
- Open the issue only after approval.
- Do not present a guess as the cause; label guesses as guesses.
SKILL.md
View file
---
name: fehlerbericht-schreiben
description: "Use this skill when an error message, log, screenshot or user complaint should become a ticket or issue."
---
# Write a bug report
A bug report that developers can start on right away.
## When to use
- When a bug was reported but described vaguely.
- Before you open an issue on GitHub or in your ticket system.
## Needs
- The error message, log excerpt, screenshot or the user’s description.
- Optional: version, device, browser, time.
## Steps
1. Sum up the bug in a title of no more than ten words.
2. Describe the expected and the actual behaviour.
3. Write numbered steps to reproduce it.
4. State the environment (version, device, browser) and attach the key line from the log.
5. Rate the severity and explain it in one sentence.
## Check before answering
- Missing details are listed as questions for the reporter.
- Personal data, tokens and passwords are removed from logs.
- One bug per report.
## Output
A bug report with "Title", "Expected", "Actual", "Steps", "Environment", "Log" and "Severity".
## Limits
- Open the issue only after approval.
- Do not present a guess as the cause; label guesses as guesses.
How to use the skill
- Create a folder
fehlerbericht-schreibenand save the file in it as SKILL.md. - Add the folder to your Grok bot or paste the content into a new conversation.
- Test the skill with a sample task before you use it regularly.