Skip to content
Back to skills

Ci Monitoring

ASecurity

Launches one attached background CI monitor for an exact pull request head.

  • 25 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 18, 2026
ai-agentsshellbashgit

Works with

  • terminal

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 18, 2026

npx -y skills add nikolanovoselec/codeflare --skill ci-monitoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ci Monitoring?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ci Monitoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nikolanovoselec-ci-monitoring/badge)](https://www.skillsdirectory.com/skills/nikolanovoselec-ci-monitoring)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ci-monitoring
description: Launches one attached background CI monitor for an exact pull request head.
version: 2.0.0
---

# Independent CI Monitoring

Launch a monitor when an automatic delivery directive or selected non-delivery review directive includes a CI wave, when the user explicitly requests monitoring, or when deploy/merge needs a fresh result. For a selected review round, issue every reviewer call first, then submit one `Agent` call with these exact fields:

```json
{
  "subagent_type": "ci-monitor",
  "description": "Monitor PR CI",
  "prompt": "{\"repo\":\"<owner/repo>\",\"pr\":<number>,\"head\":\"<full headRefOid>\",\"cwd\":\"<absolute repo root>\"}",
  "run_in_background": true
}
```

Use repository, PR, head, and cwd values from boundary directive unchanged. Dedicated agent runs seeded monitor script once with Bash timeout 600000 milliseconds; script's eight-minute deadline leaves margin for terminal output. It waits until every observed exact-head workflow is terminal and the complete fingerprint is stable across two polls. Failure output includes every failed or cancelled workflow together. Native completion begins with exactly one of `CI_RESULT success`, `CI_RESULT failure`, or `CI_RESULT timeout`, followed by `pr`, `head`, and `repo` correlation values.

Use only the hook-emitted exact plan; never independently infer identity from Git text. Successful checked-out-branch push, PR creation, and PR reopen automatically plan review plus CI. Do not detach a shell monitor, poll in root session, or duplicate an in-flight Agent. Main session owns triage and fixes; monitor only reports.

Files in this skill

  • SKILL.md1.6 KB
  • scripts/monitor-ci.mjs4.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.