ci-log-interpretation

Interpreting CI failure logs in GitHub Actions involves mapping job names and output signatures to the responsible tool. This Skill filters universal noise and provides a structured failure summary with tool attribution and actionable next steps.

Yes, identifying the failing tool is achieved through rule-based mapping from job names and output signatures. It attributes failures to specific tools like PHPUnit, PHPStan, ESLint, Jest, Playwright, or Lighthouse.

Yes, it works with PHPUnit and PHPStan errors, alongside ECS, ESLint, Jest, Playwright, Lighthouse, and ludtwig. It maps tool-specific output signatures to deliver targeted failure summaries and references.

Extracting the actual error from a noisy CI run log is done via noise filtering and context extraction. It surfaces actionable errors and run annotations while filtering out universal noise from the GitHub Actions output.