analyze-ci-failure-logs

CI failure analysis extracts error messages from logs, categorizes them by type (compilation, tests, timeout, dependency, environmental), and traces failures to source lines and stack traces. This Skill parses logs from GitHub Actions builds to surface actionable remediation steps, distinguishing code-related issues from environmental problems.

Parse CI failure logs by collecting logs from PR runs, searching for error keywords (FAILED, ERROR, PANIC, exception), and categorizing matches by failure type. Pattern-matching correlates errors with recent PR changes to produce a concise summary of root causes and remediation suggestions.

Yes, this Skill applies to CI pipelines and GitHub Actions builds. It downloads logs via the gh CLI, extracts and categorizes errors, and correlates failures with code changes to identify whether issues stem from compilation, tests, timeouts, dependencies, or environmental factors.

Use the gh CLI to download logs from a specific run: `gh run download <run-id> -D /tmp/ci-logs` or view run output: `gh run view <run-id> --log > /tmp/ci-output.log`. This Skill parses the collected logs to identify error patterns and root causes.

Categorizing CI failures by error type (compilation, tests, timeout, dependency, environmental) surfaces patterns faster than manual scanning. Automated categorization distinguishes code-related issues from environmental problems and correlates errors with recent changes, enabling faster remediation.

CI log analysis detects and categorizes compilation errors, test failures, timeouts, dependency issues, and environmental problems. It searches for error keywords (FAILED, ERROR, PANIC, exception) and traces failures to stack traces and source lines for precise root-cause identification.