# Triage Bug

> Take a raw bug report and turn it into a clean, prioritized ticket with a title, repro steps, and severity. Use when the user says "triage this", pastes a support escalation, or asks "what's this bug".

- **Type:** Skill
- **Install:** `agentstack add skill-spencerpauly-skills-repo-triage-bug`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [spencerpauly](https://agentstack.voostack.com/s/spencerpauly)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [spencerpauly](https://github.com/spencerpauly)
- **Source:** https://github.com/spencerpauly/skills-repo/tree/main/skills/triage-bug
- **Website:** https://skillsovermcp.com

## Install

```sh
agentstack add skill-spencerpauly-skills-repo-triage-bug
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Triage Bug

Convert a noisy bug report into a ticket someone can act on: one-line title, repro steps, severity, area.

## When to use

- Support escalates a bug.
- A teammate dumps a Slack thread or screenshot.
- The user says "triage this" or "what's this bug".

## Steps

1. **Re-read the report once, in full.** Don't start writing yet.
2. **Restate the symptom** in one sentence as a user would say it. No internal jargon.
3. **Pull out repro steps** even if the original report doesn't separate them. Number them 1, 2, 3.
4. **Note the gap** between expected and actual.
5. **Decide severity** with this rubric:
   - **S1** — production down, data loss, or security issue.
   - **S2** — common path broken, no workaround.
   - **S3** — broken with workaround.
   - **S4** — cosmetic / rare path.
6. **Identify the area** (one of: editor, billing, auth, api, infra, marketing).

## Output format

```markdown
## Title

## Severity
S2

## Area
billing

## Repro
1. ...
2. ...
3. ...

## Expected vs actual
- Expected: ...
- Actual: ...

## Notes
- URLs, screenshots, affected user IDs.
```

## Don't

- Don't open with "I think the issue is..." — the title goes first.
- Don't skip severity. Every ticket gets one, even if it's a guess.
- Don't paste raw stack traces into the title. Summarize.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [spencerpauly](https://github.com/spencerpauly)
- **Source:** [spencerpauly/skills-repo](https://github.com/spencerpauly/skills-repo)
- **License:** MIT
- **Homepage:** https://skillsovermcp.com

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-spencerpauly-skills-repo-triage-bug
- Seller: https://agentstack.voostack.com/s/spencerpauly
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.