bug-triage

Identify bug clusters from Sentry, support tickets, and app store reviews, then file JIRA tickets.

3|Updated May 20, 2026
One-click install
npx skills add https://github.com/iampawan/Manifest --skill bug-triage-iampawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/iampawan/Manifest/tree/main/skills/bug-triage
Command: npx skills add https://github.com/iampawan/Manifest --skill bug-triage-iampawan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sentry, atlassian, slack, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the identification of new bug clusters, deduplicates them against existing tickets, and creates JIRA tickets with proper context, thereby streamlining the bug management process.

Core Features & Use Cases

  • Bug Cluster Identification: Automatically scans Sentry, support tickets, and app store reviews for new bug clusters.
  • Deduplication: Deduplicates bugs against existing tickets to avoid duplicates.
  • JIRA Ticket Creation: Files new JIRA tickets with context, including links back to the contract revision and Sentry issue.
  • Pipeline Routing: Routes the bug back into the appropriate pipeline (trivial→/fix, substantial→/contract) with propose-by-default guardrails.
  • Use Case: For example, after a new release, the Skill can automatically identify and file new bugs found in Sentry, support tickets, and app store reviews, ensuring they are properly managed and routed.

Quick Start

Run the bug-triage skill to automatically identify and file new bugs found in Sentry, support tickets, and app store reviews.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I automate bug cluster identification across Sentry and user-facing channels?

Automate bug cluster identification by scanning Sentry, support tickets, and app store reviews to group related issues. This process deduplicates findings against existing JIRA tickets and files new ones with proper context, streamlining issue management after releases.

What's the best way to deduplicate Sentry bugs against existing JIRA tickets?

Deduplicate Sentry bugs by scanning existing JIRA tickets for matching error clusters before creating new ones. The system automatically checks current issues to avoid duplicates, filing new JIRA tickets only when unique bug clusters are identified across support tickets and app reviews.

Do I need Sentry, Atlassian, and Slack API access to automate JIRA ticket creation for bugs?

You need Sentry, Atlassian, and Slack API access to automate JIRA ticket creation for bugs. These dependencies allow the system to scan error tracking data, deduplicate against existing Atlassian tickets, and route pipeline updates through Slack notifications.

How does bug triage pipeline routing work for trivial versus substantial issues?

Bug triage pipeline routing directs trivial issues to a standard fix path and substantial issues to a contract revision path. It includes propose-by-default guardrails to route bugs back into the appropriate pipeline after creating JIRA tickets with Sentry context.