analyze-ci-failure-logs
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Best use case
analyze-ci-failure-logs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Teams using analyze-ci-failure-logs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyze-ci-failure-logs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyze-ci-failure-logs Compares
| Feature / Agent | analyze-ci-failure-logs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Analyze CI Failure Logs Parse CI failure logs to identify root causes and categorize errors. ## When to Use - CI pipeline fails and you need to understand why - Analyzing test failure logs from GitHub Actions - Extracting error messages from build artifacts - Identifying patterns in recurring failures - Determining if failure is environmental or code-related ## Quick Reference ```bash # Download CI logs from artifact gh run download <run-id> -D /tmp/ci-logs # Extract from workflow run gh run view <run-id> --log > /tmp/ci-output.log # Grep for error patterns grep -i "error\|failed\|panic\|exception" /tmp/ci-output.log # Get summary of failures tail -100 /tmp/ci-output.log | grep -A 5 "FAILED\|ERROR" ``` ## Workflow 1. **Collect logs**: Download CI artifacts or view workflow run output 2. **Extract errors**: Filter for error patterns (FAILED, ERROR, PANIC, exception) 3. **Identify type**: Categorize error (compilation, test, timeout, dependency, etc.) 4. **Find root cause**: Trace back to source (line numbers, stack traces) 5. **Check context**: Compare with recent changes in PR 6. **Create summary**: Report findings with actionable next steps ## Log Analysis Patterns **Compilation Errors**: - Look for: `error:`, `undefined`, `type mismatch` - Check: Mojo syntax, imports, type annotations **Test Failures**: - Look for: `FAILED`, `AssertionError`, `ValueError` - Check: Test logic, expected vs actual values **Timeout Issues**: - Look for: `timeout`, `timed out`, `hanging` - Check: Long-running loops, infinite recursion **Dependency Issues**: - Look for: `not found`, `import failed`, `version conflict` - Check: Package versions, environment setup **Environmental Issues**: - Look for: `permission denied`, `out of memory`, `disk full` - Check: Resource limits, configuration ## Output Format Provide analysis with: 1. **Error Category** - Type of failure (compilation, test, timeout, dependency, environmental) 2. **Root Cause** - What line/code caused the failure 3. **Context** - Full error message and stack trace 4. **Related Changes** - Which PR changes might have caused it 5. **Remediation** - Recommended fix or investigation steps ## Error Handling | Problem | Solution | |---------|----------| | Logs not accessible | Use `gh run view` to check permissions | | Truncated logs | Download full artifact instead of view | | Large log files | Use grep to extract relevant sections | | Encoded artifacts | Unzip and decompress before analysis | ## References - GitHub Actions documentation: workflow logs and artifacts - CLAUDE.md: zero-warnings policy and standards - See fix-ci-failures skill for implementing fixes
Related Skills
asciinema-analyzer
Semantic analysis of asciinema recordings. TRIGGERS - analyze cast, keyword extraction, find patterns in recordings.
analyze-state
Terraform state を分析・操作する。「state 確認」「state list」「state show」「リソース一覧」「state の移動」「state mv」「state rm」「terraform state」「state 操作」「リソースの状態」「state pull」などで起動。
analyze-source-material
Analyze mixed repositories (application code + infrastructure + policies + docs) to extract ALL components for ONE unified threat model. Use when analyzing codebases with multiple source types for threat modeling. Architecture modeling only - do NOT identify vulnerabilities.
analyze-malware
You are a malware analysis expert and you are able to understand malware for any kind of platform including, Windows, MacOS, Linux or android.
analyze-high-unemployment-high-gdp-growth-fiscal-deficit-scenarios
在「失業率走高／勞動市場轉弱」但「名目或實質 GDP 仍維持高位（或仍在成長）」的情境下，依據歷史關聯估算美國財政赤字占 GDP（Deficit/GDP）可能擴張的區間，並生成對長天期美債（長久期 UST）供給/利率風險的情境解讀。支援視覺化圖表輸出。
agentuity-cli-cloud-session-logs
Get logs for a specific session. Requires authentication. Use for Agentuity cloud platform operations
agentuity-cli-cloud-deployment-logs
View logs for a specific deployment. Requires authentication. Use for Agentuity cloud platform operations
workflow-analyzer
作業フローや手順を分析し、自動化可能な要素を特定する。ワークフロー分析時、自動化検討時、業務プロセス改善時、またはユーザーが作業フロー分析、自動化要素、業務手順、プロセス最適化に言及した際に使用する。
springboot-architecture-analyzer
系統化分析 Spring Boot 專案並生成完整的企業級架構文件,涵蓋系統概述、架構視圖、技術細節、部署策略等所有關鍵面向。
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors. Examples:\n\n<example>\nContext: Daisy has just finished implementing a new feature that fetches data from an API with fallback behavior.\nDaisy: "I've added error handling to the API client. Can you review it?"\nAssistant: "Let me use the silent-failure-hunter agent to thoroughly examine the error handling in your changes."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>\n\n<example>\nContext: Daisy has created a PR with changes that include try-catch blocks.\nDaisy: "Please review PR #1234"\nAssistant: "I'll use the silent-failure-hunter agent to check for any silent failures or inadequate error handling in this PR."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>\n\n<example>\nContext: Daisy has just refactored error handling code.\nDaisy: "I've updated the error handling in the authentication module"\nAssistant: "Let me proactively use the silent-failure-hunter agent to ensure the error handling changes don't introduce silent failures."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>
repository-analyzer
Comprehensive repository analysis using Explore agents, web search, and Context7 to investigate codebase structure, technology stack, configuration, documentation quality, and provide actionable insights. Use this skill when asked to analyze, audit, investigate, or report on a repository or codebase. | Exploreエージェント、Web検索、Context7を用いた包括的なリポジトリ分析。コードベース構造、技術スタック、設定、ドキュメント品質を調査し、実用的な洞察を提供。リポジトリやコードベースの分析、監査、調査、レポート作成を依頼された場合に使用。
project-analyzer
Automated brownfield codebase analysis. Detects project type, frameworks, dependencies, architecture patterns, and generates comprehensive project profile. Essential for Conductor integration and onboarding existing projects.