What problem does it solve?
Flaky tests in RediSearch CI waste engineering time and often go untracked or get duplicated in Jira. This Skill standardizes the reporting workflow: it collects failure evidence from GitHub Actions, finds or creates the right MOD Jira ticket, and proposes immediate triage so flaky tests are documented consistently.
Core Features & Use Cases
- Evidence Collection: Gathers failure details from GitHub Actions runs, job logs, and downloaded test artifacts using the
gh CLI, with fallbacks when --log-failed returns empty output.
- Jira Deduplication: Searches existing MOD tickets by normalized test id and
flaky_test label before creating a new Bug under the MOD-9672 epic, always asking for confirmation before mutating Jira.
- Triage & Skip Workflow: Suggests scoped test-only fixes or temporary
skip_until markers, and can prompt to dispatch the flaky-test mark workflow with explicit branch scope approval.
- Use Case: A CI run fails on
test_expire:testExpire only on macOS. Provide the run URL, and the Skill downloads the logs, identifies the likely owner from git history, finds the existing MOD ticket, and prepares a comment with the new occurrence details.
Quick Start
Report the flaky test from this failed GitHub Actions run URL and create or update the matching MOD Jira ticket.