Filing Bug Reports
Generate a standalone bug report that another developer can use to reproduce...
Install
npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Writing
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 1,808 tokens
- Runs scripts
- No, instructions only
What it does
Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.
Filing Bug Reports
Generate a self-contained bug report as a Markdown file that gives a receiving developer everything needed to reproduce the issue, without prescribing root cause or solution.
When to Use
- User asks to file, write, or document a bug
- User wants to hand off a defect for another developer to investigate
- User wants a reproducible record of unexpected behavior
When NOT to Use
- User wants to debug and fix the issue themselves right now, just help them directly
- User wants a design review or code review, use
code-reviewskill instead
Output Conventions
- File:
issues/BUG-<NNN>-<slug>.md(next available number, kebab-case slug from title) - Create the
issues/directory if it doesn't exist - One bug per file, never combine multiple bugs
Workflow
-
Reconstruct from conversation context. You were present when the bug occurred, use your conversation history to extract:
- What the user was doing (the action and intent)
- What actually happened (error messages, tool output, unexpected behavior)
- What was expected (infer from the user's goal, e.g., if they asked to read a model and got an error, expected behavior is a successful read)
-
Gather environment details programmatically. Don't ask the user for things you can look up:
- Agent workspace root, OS, architecture: from your system context
