One-click install
npx skills add https://github.com/sumpalabs/petrodb --skill triage-sumpalabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/sumpalabs/petrodb/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/sumpalabs/petrodb --skill triage-sumpalabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triaging GitHub issues is inconsistent, time-consuming, and often loses critical context like prior rejected feature requests or agent handoff specifications, leading to repeated work, misrouted issues, and wasted engineering time for maintainers.

Core Features & Use Cases

  • State machine-driven issue routing: Automatically classify issues as bugs or enhancements, then assign canonical state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to ensure consistent, predictable workflow progression.
  • Durable agent brief generation: Create path-agnostic, behavior-focused specifications for issues ready for AFK agents, avoiding stale file path or line number references that break as the codebase evolves.
  • Out-of-scope knowledge base: Track rejected feature requests in a structured directory to preserve institutional reasoning and surface prior rejections when similar new issues are submitted, preventing re-litigation of settled decisions.
  • Use Case: Open source maintainers handling high volumes of GitHub issues can use this skill to automate initial classification, ensure consistent routing, and reduce repetitive work on previously rejected feature requests.

Quick Start

Ask the triage skill to list all GitHub issues requiring your attention, sorted by oldest first, with one-line summaries for each.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue triage for high volumes of bugs and feature requests?

Automate GitHub issue triage by applying a state machine that classifies issues as bugs or enhancements and assigns canonical state roles like needs-triage, needs-info, and wontfix, ensuring consistent routing and predictable workflow progression for software engineering teams.

How does an out-of-scope knowledge base prevent duplicate work on rejected feature requests?

An out-of-scope knowledge base tracks rejected feature requests in a structured directory to preserve institutional reasoning. It surfaces prior rejections when similar new issues are submitted, preventing the re-litigation of settled decisions and reducing wasted engineering time.

Can I generate agent briefs for GitHub issues without referencing stale file paths?

Yes, you can generate durable agent briefs that are path-agnostic and behavior-focused, avoiding stale file path or line number references that break as the codebase evolves and ensuring reliable AFK agent handoff for issue implementation.

What is the best way to route GitHub issues between human maintainers and AFK agents?

The best way to route GitHub issues is using state-driven routing that assigns canonical state roles such as ready-for-agent and ready-for-human, ensuring issues are directed to the correct handler without losing critical context.

Does this issue triage workflow work for both open source and internal project bug tracking?

Yes, this issue triage workflow applies to both open source and internal project workflows involving bug tracking and feature request management. It solves inconsistent manual triage and context loss for any software engineering team handling GitHub issues.