test-log-analyst

Analyzes CI logs and produces incremental failure reports with remediation suggestions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill test-log-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-log-analyst
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/test-log-analyst
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill test-log-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and automates analysis of failing test runs so developers and CI engineers do not need to manually inspect disparate logs and reports to find root causes. It turns pytest, Vitest, Playwright, Wokwi and CI artifacts into concise failure summaries, actionable recommendations, and file-level pointers.

Core Features & Use Cases

  • Multi-framework parsing: Parses JUnit XML, HTML Playwright reports, coverage outputs, Wokwi JSON/junit, and plain-text pytest logs to locate failing testcases and stack traces.
  • CI artifact handling: Uses gh CLI patterns to list failing runs, download artifacts, and extract logs for comparison between CI and local executions.
  • Consolidated reporting: Produces and incrementally updates .claude/reports/Testrunner/test.md with a summary, per-area sections (backend, frontend, E2E, Wokwi), and next-step recommendations.
  • Use case: When a GitHub Actions run fails for server-tests, the Skill downloads the unit-test-results artifact, extracts junit-*.xml, highlights failing tests, and suggests focused reproduction commands and likely fixes.

Quick Start

Analyze the failing tests in logs/backend/pytest-results.xml and update .claude/reports/Testrunner/test.md with a concise summary of failures and recommended next steps.

Frequently Asked Questions about test-log-analyst

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

FAQPage Schema
How do I analyze pytest test failures from JUnit XML logs?

You can analyze pytest test failures by parsing JUnit XML files to extract failing testcases, stack traces, and file paths, generating a consolidated report with remediation suggestions without manual log inspection.

Can I download and analyze GitHub Actions artifacts for failing Vitest runs?

Yes, you can download and analyze GitHub Actions artifacts for failing Vitest runs by using gh CLI patterns to list failing runs, extract logs, and compare CI executions with local runs to produce concise failure summaries and recommended next steps.

What is the best way to parse Playwright HTML reports and traces for E2E test failures?

Parsing Playwright HTML reports and traces involves extracting failure details and stack traces from the HTML outputs to incrementally update a markdown report with per-area sections and focused reproduction commands for E2E test failures.

Does this approach work with Wokwi JSON and JUnit outputs for unit tests?

Yes, this approach works with Wokwi JSON and JUnit outputs by parsing them alongside pytest, Vitest, and Playwright logs to locate failing testcases and generate file-level pointers with actionable recommendations for both unit and end-to-end scenarios.

How do I consolidate test and CI logs into a single incremental failure report?

You consolidate test and CI logs by parsing JUnit XML, HTML reports, coverage outputs, and gh run logs to produce and incrementally update a markdown file with summaries, per-area sections for backend and frontend, and next-step recommendations.