triage-flaky-tests

Creates Jira Bug tickets for untriaged flaky tests from a Confluence hub page.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill triage-flaky-tests-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-flaky-tests
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/flaky-test-triage/skills/triage-flaky-tests
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill triage-flaky-tests-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flaky test entries recorded on a Confluence hub page often sit untriaged with no Jira ticket, so they never get prioritized or fixed. This Skill reads the CPOMS StudentSafe Flaky Tests Hub page, identifies rows without a linked Jira issue, and creates properly formatted AI project Bug tickets for each one, then writes the Jira links back to the page. ## Core Features & Use Cases - Untriaged Row Detection: Parses the Confluence page's storage HTML to find table rows lacking a Jira smart-link macro or AI issue anchor, avoiding false positives from markdown rendering. - Structured Ticket Creation: Reads the referenced spec file, drafts an objective Bug description (test scenario, interactions, current vs expected behavior), gets user approval, and creates the ticket via jira-cli or the Atlassian MCP with fixed project, priority, component, and label defaults. - Page Write-Back: Updates each row's Jira cell with a smart-link macro and pushes a single Confluence page update after all tickets are created. - Use Case: A QA engineer opens the flaky tests hub, sees 12 untriaged entries, and runs this Skill to walk through each one, approve drafted tickets, and end with every row linked to an AI Bug ticket. ## Quick Start Triage the untriaged flaky tests from the Confluence hub page and create Jira Bug tickets for each one.

Frequently Asked Questions about triage-flaky-tests

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

FAQPage Schema
How do I create Jira tickets for flaky tests from a Confluence page?

Run this Skill to fetch the Flaky Tests Hub Confluence page, detect rows without a linked Jira issue, and draft a Bug ticket per row. After you approve each draft, it creates the ticket via jira-cli or the Atlassian MCP and writes the issue link back to the page.

How does the skill detect which flaky tests are already triaged?

It inspects the Confluence storage HTML for each row's Jira cell, checking for a Jira smart-link macro (ac:name="jira") or an anchor link to an AI issue. Markdown output is not trusted because it silently strips smart-link macros, making triaged rows look untriaged.

Can I use this without installing jira-cli or confluence-cli?

Yes. The CLI tools are preferred for lower cost, but if either is missing the Skill offers to fall back to the Atlassian MCP tools (getConfluencePage, updateConfluencePage, createJiraIssue) instead of halting.

What Jira fields are set on the created flaky test tickets?

Tickets are created in the AI project as Bug type with P4 priority, the StudentSafe component, the flaky-test label, and the Found By field set to Engineering Team (Dev/QA). The summary follows the format 'Flaky spec: <exact failed example name>'.

Why does the ticket description exclude root cause analysis?

The Skill enforces objective descriptions covering only the test scenario, interactions, and current versus expected behavior. Notes from the Confluence table are filtered to keep only factual references to commits, MRs, or deploys, excluding speculation and opinions.