add-flaky-test-to-hub

Adds flaky test entries to a Confluence hub page from CI job failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recording flaky tests manually in a shared tracking page is error-prone and inconsistent. This Skill automates adding a new flaky test entry to the CPOMS StudentSafe Flaky Tests Hub Confluence page, pulling failure context directly from the GitLab CI job output. ## Core Features & Use Cases - Automated Row Creation: Builds a properly formatted 11-column Confluence storage-format table row with unique UUIDs, date, and reporter account ID. - CI Failure Context Extraction: Fetches the GitLab pipeline job output and quotes verbatim failure messages (including retry failures) in the Notes cell. - Dual Tooling Support: Uses confluence-cli as the primary method with an Atlassian MCP fallback for reading and updating the page. - Use Case: After noticing a flaky RSpec test fail in CI, provide the test file path with line number and the CI job URL; the Skill reads the test, extracts the failure, and appends a reviewed row to the hub page with status Reported. ## Quick Start Add the flaky test at spec/system/incidents/jsh_spec.rb:46 from CI job URL https://gitlab.com/trigent1/trigent/cpoms/cpoms/-/jobs/14164288388 to the flaky tests hub.

Frequently Asked Questions about add-flaky-test-to-hub

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

FAQPage Schema
How do I add a flaky test to the Confluence tracking hub?

Provide the test file path with line number and the CI job URL, then confirm the previewed row. The Skill reads the test, fetches the CI failure output, and appends a formatted row to the hub page with status Reported.

How do I record a flaky test without a CI job URL?

Enter none instead of a CI job URL when prompted. The pipeline cell is left empty and the Notes cell uses an empty paragraph tag, since no factual CI failure content is available.

Can I use this without confluence-cli installed?

Yes, the Skill falls back to the Atlassian MCP tools for fetching and updating the Confluence page. You will need to provide your Atlassian account ID manually since the CLI config is unavailable.

What goes into the Notes cell for a flaky test entry?

Only verbatim failure messages from the CI job's Failure block, quoted in code tags, plus retry failure messages if meaningfully different. Speculation, opinions, and vague notes are excluded.

Why are the Jira issue and MR columns empty on new entries?

New entries always start with empty Jira issue and MR cells and status Reported. Those fields are filled in later by the separate triage-flaky-tests skill during backlog triage.