agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/qa-release/crash-triage/SKILL.md

crash-triage

Skill105 starsChanged 8 months agoMITView on GitHub

Handle crashes as high-severity defects with reproducibility, symbol quality, clustering, and release impact in mind.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    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:

    check if symbols and build metadata are sufficient

    line 27
  2. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  3. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Crash Triage

Purpose

Handle crashes as high-severity defects with reproducibility, symbol quality, clustering, and release impact in mind.

Use When

  • crashes are reported in QA or live builds
  • stack traces are noisy
  • the team needs root-cause prioritization

Inputs

  • crash dumps or logs
  • build symbols
  • repro steps if any
  • frequency and environment data

Process

  1. group crashes by likely signature and root cause
  2. separate deterministic repros from low-signal incidents
  3. check if symbols and build metadata are sufficient
  4. identify release blockers and likely owner systems
  5. track verification once fixes land

Outputs

  • crash cluster report
  • owner assignment
  • repro notes
  • release impact summary

Quality Bar

  • turns risk into explicit evidence and ownership
  • keeps release blockers visible instead of implicit
  • connects quality decisions to milestone and platform impact

Common Failure Modes

  • severity inflation or minimization without player-impact context
  • treating waived risks as invisible
  • submission checklists that are incomplete or stale

Related Agents

  • qa-lead
  • build-engineer
  • release-manager

Related Commands

  • bug-triage
  • release-check
  • verify

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

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