parse-error-logs

Parse npm, pnpm, TypeScript, Jest, and build logs into structured JSON reports.

243|40|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parse-error-logs
Source: https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs
Command: npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts raw error logs from builds, tests, and validations into structured JSON data to accelerate debugging and quality gates.

Core Features & Use Cases

  • Pattern-based parsing: Detect TypeScript, Jest, npm, and build error formats.
  • Structured extraction: Capture file, line, code, message, and severity for each error.
  • Reporting: Produce aggregated summaries of errors and warnings for quality gates.

Quick Start

Input a sample log output and receive a JSON object with error items and a summary.

Frequently Asked Questions about parse-error-logs

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

FAQPage Schema
How do I parse error logs from TypeScript, Jest, and npm builds into structured data?

Parse error logs by extracting file paths, line numbers, error codes, and messages from TypeScript, Jest, and npm output into a JSON report. This Skill detects error patterns across build tools and returns structured data with file location, severity, and error type for each issue.

Can I use error log parsing to enforce quality gates in CI pipelines?

Yes. Convert raw build and test output into structured JSON with error counts and severity summaries. Quality gates can then programmatically check error thresholds, pass/fail criteria, and categorized results before merging or deploying.

What error formats does this support?

This Skill parses TypeScript compiler errors, Jest test failures, npm/pnpm validation output, and generic build logs. It extracts file, line, column, code, message, and severity from each format and categorizes errors by type.

How do I extract specific error details for debugging?

Input error log output and receive a complete JSON report containing individual error items with file location, line and column numbers, error code, message text, and severity level—ready to feed into debugging workflows or downstream CI tasks.

What's the output format when parsing validation logs?

Error log parsing produces a JSON object with an array of error items (each with file, line, code, message, severity) and a summary section containing total error count, warning count, and categorization by error type.

Does this work with logs from multiple tools in one pipeline?

Yes. Parse error output from npm, pnpm, TypeScript, Jest, and build tools in a single workflow. The pattern-based parser detects and extracts errors from each tool's format and returns unified JSON data across all sources.