extract-test-failures

Parse test logs to extract and categorize failures by type.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ProjectOdyssey --skill extract-test-failures
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: extract-test-failures
Source: https://github.com/mvillmow/ProjectOdyssey/tree/main/.claude/skills/extract-test-failures
Command: npx skills add https://github.com/mvillmow/ProjectOdyssey --skill extract-test-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill requires grep, sort, uniq, tail.

What problem does it solve?

Sifting through large test logs to identify, categorize, and understand failures is time-consuming and inefficient, delaying debugging efforts.

Core Features & Use Cases

  • Failure Extraction: Parses test logs to extract failure information, including test names, error types, and stack traces.
  • Summary Reporting: Creates a concise summary report of failures, categorizing them by type (assertion, runtime, timeout).
  • Use Case: When a CI test run fails with hundreds of lines of output, use this skill to quickly extract and summarize the failed tests and their error messages, pinpointing the most critical issues.

Quick Start

Use the extract-test-failures skill to extract and summarize all failed test names from 'test_output.log'.

Frequently Asked Questions about extract-test-failures

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

FAQPage Schema
How do I extract test failures from CI pipeline logs?โ–ผ

Extract test failures by parsing logs to identify FAILED markers, error messages, and stack traces. This skill analyzes test output, categorizes failures by type (assertion, runtime, timeout), and produces a structured summary report pinpointing which tests failed and why.

How can I quickly summarize hundreds of failed tests from log output?โ–ผ

Parse test logs to extract failure details, then generate a concise summary that counts totals, identifies patterns, and organizes failures by error type. This reduces time spent manually reviewing large test suites to locate critical issues.

What's the best way to categorize test failures by type?โ–ผ

Analyze logs to detect and classify failures into assertion errors, runtime exceptions, and timeout failures. Categorization groups related failures together, making it easier to identify systematic problems versus isolated test issues.

Can I use grep and sort to analyze test failure logs?โ–ผ

Yes. This skill leverages grep, sort, uniq, and tail to parse logs, extract failure markers, deduplicate entries, and isolate relevant stack traces. These utilities work together to filter and structure raw test output into actionable reports.

How do I detect patterns in repeated test failures?โ–ผ

Extract and count failure occurrences across log files using deduplication and aggregation. Pattern detection reveals which error types dominate, whether failures cluster around specific test modules, and which issues recur most frequently.