Skip to content
Skills Library
Programming · Analysis

test-intelligence

/test-intelligence

Pull and analyze test results from a Semaphore pipeline — failure detail, flaky-test detection, JUnit parsing. Use when a job failed and you need to see WHICH test broke without changing the pipeline config or re-running; when a junit-only reporter hides failure detail in the log; when you're about to add a stdout reporter just to debug — pull the published JUnit artifact instead via `sem-ai test summary` / `sem-ai test report` / `sem-ai artifact get`. Supports Go, pytest, rspec, minitest, jest, ExUnit.

Repository
sem-ai ↗
Licence
Apache-2.0
Last repository change
06.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Pull and analyze test results from a Semaphore pipeline — failure detail, flaky-test detection, JUnit parsing. Use when a job failed and you need to see WHICH test broke without changing the pipeline config or re-running; when a junit-only reporter hides failure detail in the log; when you're about to add a stdout reporter just to debug — pull the published JUnit artifact instead via `sem-ai test summary` / `sem-ai test report` / `sem-ai artifact get`. Supports Go, pytest, rspec, minitest, jest, ExUnit.

Original author description

Pull and analyze test results from a Semaphore pipeline — failure detail, flaky-test detection, JUnit parsing. Use when a job failed and you need to see WHICH test broke without changing the pipeline config or re-running; when a junit-only reporter hides failure detail in the log; when you're about to add a stdout reporter just to debug — pull the published JUnit artifact instead via `sem-ai test summary` / `sem-ai test report` / `sem-ai artifact get`. Supports Go, pytest, rspec, minitest, jest, ExUnit.

How it works

  1. Quick summary
  2. Detailed per-job report
  3. Flaky detection
  4. Common workflows
Original SKILL.md headings · 53 lines, 176 words
SKILL.md preview
---
name: test-intelligence
description: Pull and analyze test results from a Semaphore pipeline — failure detail, flaky-test detection, JUnit parsing. Use when a job failed and you need to see WHICH test broke without changing the pipeline config or re-running; when a junit-only reporter hides failure detail in the log; when you're about to add a stdout reporter just to debug — pull the published JUnit artifact instead via `sem-ai test summary` / `sem-ai test report` / `sem-ai artifact get`. Supports Go, pytest, rspec, minitest, jest, ExUnit.
user-invocable: false
---

# Test Intelligence

## Quick summary
```bash
sem-ai test summary --pipeline <id>
```
Returns: verdict, total/passed/failed/skipped, failures with test name + file:line + message.

## Detailed per-job report
```bash
sem-ai test report --pipeline <id>
```
Each job shows: framework detected, source (artifact or log), counts, failed test details.

**Strategy:** tries artifact JUnit JSON first (richer data), falls back to log parsing.

**Frameworks:** Go/gotestsum, pytest, rspec, minitest, jest, ExUnit, JUnit JSON.

## Flaky detection
```bash
sem-ai test flaky --project my-app --branch main --count 10
```
Analyzes last N workflows. Flaky = test that sometimes passes, sometimes fails.

## Common workflows

**"Did tests pass?"**
```bash
sem-ai test summary --pipeline <id>   # check "verdict" field
```

**"Which test broke?"**
```bash
sem-ai test summary --pipeline <id>   # check "failures" array
```

**"Is this flaky?"**
```bash
sem-ai test flaky --project <p> --count 10
# Cross-reference failing test name with flaky_tests list
```

**"Get raw test artifact"**
```bash
sem-ai artifact get --scope jobs --id <job-id> --path test-results/junit.json --output results.json
```

**"Show raw test output"**
```bash
sem-ai job log <job-id> --format table
```

Versions

The database has no other skills named test-intelligence.

Database snapshot: 13.11.2026 · package version 97c778285d4d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100semaphore-test-results
    Publish JUnit test reports from Semaphore jobs and surface them in the UI's Test Reports tab. Covers the `test-results` CLI, why it must live in `epilogue` (not the test command itself), and per-framework JUnit configuration for Go, pytest, RSpec, Jest, Vitest, ExUnit, Java. Use…
  • 100semaphore-ci
    Manage Semaphore CI/CD via sem-ai. Use when the user asks about CI status, pipeline failures, test results, deployments, secrets, notifications, scheduled tasks, deployment targets, project health, or anything related to their Semaphore pipelines and workflows — e.g. "CI…
  • 100test-runner
    Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
  • 100test-analyze
    Analyze test results and create a fix plan with subagents. Use when triaging failing tests, analyzing JUnit XML, planning fixes for accessibility/security, or categorizing flaky/E2E failures.
  • 100junit-extensions
    Use when jUnit extensions including custom extensions, rules, and conditional test execution.
  • 90java-junit
    JUnit 5 testing patterns and parameterized-test guidance. Use when writing or reviewing Java unit tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.