Menu

Individual skill

issue-triage

0upvotes

Triaging error reports — prioritization, ownership, and keeping the backlog actionable — works with any error tracker.

skills/issue-triage/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

An error tracker without triage becomes a write-only database of sadness:
thousands of open issues, nobody looking. Triage is the discipline of
regularly reviewing new errors, assigning ownership, and keeping the backlog
a true reflection of product health. This skill covers the process.

## When to use

- Setting up a triage rotation or process for error reports
- Prioritizing which errors to fix first (frequency × severity)
- Defining ownership of errors across teams/services
- Reducing a massive untriaged backlog to something manageable
- Deciding when to ignore, mute, or archive error issues
Back to top