rai-bugfix-triage

Classify bugs into four dimensions and persist to scope.md and Jira custom fields.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-bugfix-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-bugfix-triage
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-bugfix-triage
Command: npx skills add https://github.com/humansys/raise --skill rai-bugfix-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents downstream analysis and remediation errors by ensuring every bug is consistently classified across four orthogonal dimensions and the classification is persisted in both the scope artifact and Jira custom fields.

Core Features & Use Cases

  • Four-dimension classification: Captures Bug Type, Severity, Origin, and Qualifier to make bug data queryable and analysis-safe.
  • Jira synchronization: Updates four Jira custom fields via MCP with a manual UI fallback if MCP is unavailable.
  • Auditable commit: Appends a TRIAGE block to work/bugs/RAISE-{N}/scope.md and commits the change to preserve provenance.
  • Use case: Use on a reproducible bug branch after a scope.md is created to ensure mandatory triage before analysis.

Quick Start

Run the rai-bugfix-triage skill for bug RAISE-123 to classify it in four dimensions and update the Jira custom fields and scope artifact.

Frequently Asked Questions about rai-bugfix-triage

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

FAQPage Schema
How do I classify bugs into orthogonal dimensions for Jira triage?

Bug triage classifies defects across four orthogonal dimensions—Bug Type, Severity, Origin, and Qualifier—and persists the classification to Jira custom fields and the project's scope artifact to make bug data queryable and analysis-safe.

Why do I need a scope.md file before running bug triage on a defect branch?

Bug triage requires a work/bugs/RAISE-{N}/scope.md file without an existing TRIAGE block to append the classification provenance and commit the change, ensuring mandatory triage occurs before analysis.

What is the best way to synchronize bug triage classifications with Jira when MCP is unavailable?

Bug triage updates four Jira custom fields via MCP by default, but provides a manual UI fallback to update fields directly if MCP access is unavailable.

Does bug triage work with existing Jira custom fields for bug tracking?

Yes, bug triage updates four Jira custom fields via MCP integration, persisting Bug Type, Severity, Origin, and Qualifier classifications directly into your existing Jira project configuration.

When should I run bug triage during the bugfix workflow?

Run bug triage on a reproducible bug branch after scope.md is created and before analysis begins, ensuring every defect receives mandatory four-dimension classification to prevent downstream remediation errors.

How does bug triage preserve classification provenance in the repository?

Bug triage appends a TRIAGE block to work/bugs/RAISE-{N}/scope.md and commits the change using git permissions, preserving an auditable record of the four-dimension classification alongside the project scope artifact.