How do I install the Ci:monitoring skill?

Run npx skillmds add majiayu000/ci-monitoring-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ci:monitoring skill do?

Monitor running CI jobs, wait for completion, create tasks for results It is listed under Coding & Dev Tools on SkillMD.

Is Ci:monitoring safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ci:monitoring?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ci:monitoring free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ci:monitoring?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ci:monitoring by majiayu000 — Agent Skill

Name: Ci:monitoring
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

CI Monitoring

Monitor running CI pipelines and report results. Creates task items for each CI check being monitored.

When to Use

After pushing to a PR, to track CI completion
When user says "monitor CI" or "check CI"
When waiting for HyperShift E2E (long-running, needs manual trigger)
To track multiple CI checks in parallel

Workflow

1. Create Monitoring Tasks

For each pending CI check, create a task:

TaskCreate: "<worktree> | <PR> | CI | Monitor | <check-name>"
  metadata: plan="ad-hoc", runner="main-session"

Example:

#33 [in_progress] mlflow-ci | PR#569 | CI | Monitor | Kind Deploy & Test
#34 [pending]     mlflow-ci | PR#569 | CI | Monitor | HyperShift E2E

2. Check Status Periodically

gh pr checks <PR-number>

3. On Completion

For each check that completes:

Mark monitoring task as completed
If passed: note in task description
If failed: create RCA task and invoke rca:ci

TaskUpdate: #33 status=completed
TaskCreate: "<worktree> | <PR> | Kind CI | RCA | <failure summary>"

4. Report Summary

Present final status table:

#	Check	Status	Action
#33	Kind Deploy & Test	passed	-
#34	HyperShift E2E	failed	→ #35 RCA created
#35	Kind CI	RCA	Agent empty response

CI Check Types

Check	Trigger	Duration	Manual?
CodeQL	Auto on push	~2 min	No
Deploy & Test (Kind)	Auto on push	~12 min	No
E2E HyperShift	`/test` comment	~45 min	Yes
Build, Lint, Security	Auto on push	~1 min	No

HyperShift E2E

HyperShift requires manual trigger:

# Trigger via PR comment (done by user in GitHub UI)
# The workflow responds to issue_comment with "/test"

Monitor:

gh run view <run-id> --json status --jq '.status'
gh run view <run-id> | head -25

Task Tracking

On invocation:

TaskList - find existing CI monitoring tasks for this PR
Update completed checks
Create new monitoring tasks for pending checks
For failures, create RCA tasks linked to rca:ci or rca:hypershift

Naming: <worktree> | <PR> | CI | Monitor | <check-name>

Troubleshooting

HyperShift not starting

Needs /test comment on PR
Check if previous run is still cleaning up
Check slot availability: CI has limited concurrent HyperShift clusters

CI running on old commit

Push triggers new run on latest commit
Old runs may still be in progress
Check headSha matches expected commit

Related Skills

ci:status - One-time status check
rca:ci - RCA when CI fails
tdd:ci - TDD iteration using CI
tdd:kind - Local Kind testing (faster feedback)

---name: ci-monitoring-2description: Monitor running CI jobs, wait for completion, create tasks for results--- # CI Monitoring Monitor running CI pipelines and report results. Creates task items for each CI check being monitored. ## When to Use - After pushing to a PR, to track CI completion - When user says "monitor CI" or "check CI" - When waiting for HyperShift E2E (long-running, needs manual trigger) - To track multiple CI checks in parallel ## Workflow ### 1. Create Monitoring Tasks For each pending CI check, create a task: ``` TaskCreate: "<worktree> | <PR> | CI | Monitor | <check-name>" metadata: plan="ad-hoc", runner="main-session" ``` Example: ``` #33 [in_progress] mlflow-ci | PR#569 | CI | Monitor | Kind Deploy & Test #34 [pending] mlflow-ci | PR#569 | CI | Monitor | HyperShift E2E ``` ### 2. Check Status Periodically ```bash gh pr checks <PR-number> ``` ### 3. On Completion For each check that completes: - Mark monitoring task as `completed` - If **passed**: note in task description - If **failed**: create RCA task and invoke `rca:ci` ``` TaskUpdate: #33 status=completed TaskCreate: "<worktree> | <PR> | Kind CI | RCA | <failure summary>" ``` ### 4. Report Summary Present final status table: | # | Check | Status | Action | |---|-------|--------|--------| | #33 | Kind Deploy & Test | passed | - | | #34 | HyperShift E2E | failed | → #35 RCA created | | #35 | Kind CI | RCA | Agent empty response | ## CI Check Types | Check | Trigger | Duration | Manual? | |-------|---------|----------|---------| | CodeQL | Auto on push | ~2 min | No | | Deploy & Test (Kind) | Auto on push | ~12 min | No | | E2E HyperShift | `/test` comment | ~45 min | Yes | | Build, Lint, Security | Auto on push | ~1 min | No | ## HyperShift E2E HyperShift requires manual trigger: ```bash # Trigger via PR comment (done by user in GitHub UI) # The workflow responds to issue_comment with "/test" ``` Monitor: ```bash gh run view <run-id> --json status --jq '.status' gh run view <run-id> | head -25 ``` ## Task Tracking On invocation: 1. TaskList - find existing CI monitoring tasks for this PR 2. Update completed checks 3. Create new monitoring tasks for pending checks 4. For failures, create RCA tasks linked to `rca:ci` or `rca:hypershift` Naming: `<worktree> | <PR> | CI | Monitor | <check-name>` ## Troubleshooting ### HyperShift not starting - Needs `/test` comment on PR - Check if previous run is still cleaning up - Check slot availability: CI has limited concurrent HyperShift clusters ### CI running on old commit - Push triggers new run on latest commit - Old runs may still be in progress - Check `headSha` matches expected commit ## Related Skills - `ci:status` - One-time status check - `rca:ci` - RCA when CI fails - `tdd:ci` - TDD iteration using CI - `tdd:kind` - Local Kind testing (faster feedback)

Frequently asked questions