agentleFS
Sign inStart free
spencerpaulyspencerpauly/skills-repo/skills/triage-bug/SKILL.md

triage-bug

Skill25 starsChanged 7 months agoMITView on GitHub

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".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Hakktivist/claude-skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Re-read the report once, in full: Don't start writing yet.

    line 19
  2. Distinctive:

    Don't open with "I think the issue is..." — the title goes first.

    line 57
  3. Distinctive:

    Don't skip severity. Every ticket gets one, even if it's a guess.

    line 58
  4. Distinctive:

    Don't paste raw stack traces into the title.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

## Title
<one line, present tense, no "bug:" prefix>

## 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free