issue-triage

Classify and route Pact project issues by type and priority.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill issue-triage-pact-community-organization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/issue-triage
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill issue-triage-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly organize and route Pact project issues, reducing time-to-triage and improving first-contact resolution.

Core Features & Use Cases

  • Automated classification: identify issue type (security, bug, docs, enhancement) and route to the correct owner.
  • Priority guidance: assign initial priority (P0-P3) and verify duplicates.
  • Initial diagnosis scaffold: collect reproduction steps, affected components, and summary for handoff.

Quick Start

Classify and route incoming Pact issues by type and priority, then present an initial diagnosis to the coordinating Admin agent.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I automate issue triage and routing for incoming project reports?

Automated issue triage classifies incoming bug reports, security alerts, and feature requests to determine type, initial priority (P0-P3), and routing paths to the correct owner for faster resolution.

What is the best way to classify and prioritize security alerts versus enhancement requests?

Classifying and prioritizing issues involves identifying the type, assigning an initial priority from P0 to P3, verifying duplicates, and routing security alerts or enhancements to the appropriate specialist team.

How do I collect reproduction steps and affected components for issue diagnosis?

Initial issue diagnosis scaffolds collect reproduction steps, affected components, and summaries during triage, providing a structured handoff for the coordinating Admin agent to resolve the report.

Can I manage issue labels and check for duplicates automatically during triage?

Issue label management and duplicate checks are supported during deterministic triage steps, ensuring reports are classified correctly before routing to the correct specialist.

Does issue triage work with feature requests and documentation bugs?

Issue triage works with feature requests and documentation bugs by applying classification logic to identify the issue type and route it to the appropriate team for resolution.

When should I not use automated issue classification for routing?

Automated issue classification should not be used when reports lack sufficient detail for initial diagnosis scaffolding, as accurate routing and priority assignment require reproduction steps and affected components.