# Filing Bug Reports

Generate a standalone bug report that another developer can use to reproduce...

- Repository: https://github.com/matlab/simulink-agentic-toolkit (1305 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -g -a claude-code -y`
Codex: `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -g -a codex -y`
Cursor: `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -g -a cursor -y`
Gemini CLI: `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add matlab/simulink-agentic-toolkit`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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-review` skill 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

1. **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)

2. **Gather environment details programmatically.** Don't ask the user for things you can look up:
   - Agent workspace root, OS, architecture: from your system context

The rest: https://github.com/matlab/simulink-agentic-toolkit/blob/HEAD/skills-catalog/model-based-design-core/filing-bug-reports/SKILL.md