Diagnose CI/CD failures by analyzing ci-summary.json build artifacts.
npx skills add https://github.com/ethosengine/elohim --skill ci-triage
Please help me install this Agent Skill. Skill: ci-triage Source: https://github.com/ethosengine/elohim/tree/main/.claude/skills/ci-triage Command: npx skills add https://github.com/ethosengine/elohim --skill ci-triage
Quick CI/CD failure diagnosis to accelerate debugging and reduce MTTR when builds fail.
Use the ci-triage skill to inspect a failing elohim orchestrator build and fetch the ci-summary.json artifact.
High-intent search queries and answers about installing and using this skill.
To diagnose a CI/CD build failure, you can use guided triage workflows that apply category-specific search patterns and analyze build artifacts to surface actionable root-cause insights.
Build artifacts like ci-summary.json are fetched and analyzed to reproduce issues and guide remediation, providing deterministic data access to identify common failure points in your pipeline.
To reduce MTTR for broken CI pipelines, apply targeted artifact-based analysis and category-specific search patterns that quickly narrow down failure points and propose actionable fixes.
Yes, applying category-specific search patterns during triage narrows down CI failure diagnostics by directing the investigation toward specific build issue categories and artifact data.
No specific dependencies are required for this CI triage approach; it relies on deterministic steps and artifact-based data access to reproduce issues across failing CI pipelines.
You should avoid artifact-based CI failure triage when build artifacts like ci-summary.json are unavailable, as the process depends on fetching these artifacts to reproduce issues and guide remediation.
mako-aiAutomate build, test, packaging, and release workflows for Mako Desktop and Local Agent.
ThejanaJayalathDiagnose AI agent execution failures through structured root-cause analysis.
serejarisFetch raw API data and generate structured digests locally.
jhlee0409Analyze code and trace execution flows in read-only mode.
