ci:monitoring

Monitor GitHub Actions CI checks and create RCA tasks on failure.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill ci-monitoring-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci:monitoring
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/ci%3Amonitoring
Command: npx skills add https://github.com/kagenti/kagenti --skill ci-monitoring-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the monitoring of Continuous Integration (CI) jobs, ensuring timely reporting of their status and facilitating root cause analysis for failures.

Core Features & Use Cases

  • CI Job Monitoring: Tracks the progress of various CI checks (e.g., CodeQL, Deploy & Test, E2E HyperShift).
  • Status Reporting: Provides a clear summary of passed or failed CI checks.
  • Failure RCA: Automatically creates tasks for root cause analysis (RCA) when CI checks fail, invoking related skills like rca:ci.
  • Use Case: After pushing a code change to a pull request, this Skill can be used to automatically monitor all associated CI checks, notify you of their completion, and initiate an RCA process if any check fails.

Quick Start

Use the ci:monitoring skill to track the status of CI checks for the current pull request.

Frequently Asked Questions about ci:monitoring

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

FAQPage Schema
How do I monitor GitHub Actions CI checks for a pull request?

To monitor GitHub Actions CI checks for a pull request, this skill tracks running jobs, waits for completion, and provides a clear summary of passed or failed statuses. It handles various checks including long-running tasks like E2E HyperShift tests.

Can I automate root cause analysis when a CI job fails?

Yes, you can automate root cause analysis for CI failures. When CI checks fail, this skill automatically creates tasks for RCA and invokes related analysis skills to investigate the failure, ensuring timely feedback.

How does CI monitoring handle long-running E2E tests?

CI monitoring handles long-running E2E tests by continuously tracking the progress of jobs like HyperShift E2E until completion. It manages task creation and updates based on job statuses to ensure you receive timely final results.

What is the best way to track CI job statuses and report results?

The best way to track CI job statuses and report results is using an automated monitoring skill that waits for job completion and generates clear status summaries. This ensures timely reporting without manual checks.

Does CI monitoring support CodeQL and Deploy & Test checks?

Yes, CI monitoring supports tracking CodeQL and Deploy & Test checks. It monitors the progress of various GitHub Actions CI checks for pull requests and reports whether they pass or fail.