Automated summary
A routing skill that dispatches CI work on GitHub Actions to the right sub-skill: status check, monitoring, root-cause analysis, or fix-and-rerun.
Strengths
- Explicit decision diagram mapping each situation (check, wait, investigate, fix) to a dedicated sub-skill
- Relies on the standard `gh pr checks` command, so it is quick to adopt
- Cleanly separates diagnosis (rca:ci) from iterative fixing (tdd:ci), keeping investigation and code changes apart
- Covers the full loop through merge: status → failure → root cause → fix → green CI
Limitations
- Contains almost no logic of its own: it delegates to `ci:status`, `ci:monitoring`, `rca:ci` and `tdd:ci`, which must be installed separately
- Scoped to GitHub Actions and an authenticated `gh` CLI; no GitLab CI, Jenkins, or CircleCI support
- Sub-skill selection depends on the context the user supplies rather than real detection of pipeline state
Use it whenever a push or pull request triggers a GitHub CI run and you need to know the pipeline state or what to do about a failure.
Avoid it if your CI is not GitHub Actions or if the ci:status, ci:monitoring, rca:ci and tdd:ci sub-skills are not available in your environment.
Security analysis
SafeThe skill is a workflow router for CI-related sub-skills and only suggests a read-only GitHub CLI command (`gh pr checks`). It declares no tools and contains no destructive, exfiltrating, or obfuscated actions.
No concerns found
How this analysis is madeExamples
Check the CI status on my current PR and tell me exactly which checks failed and why.Monitor the GitHub Actions run on this branch until it finishes, then summarize the results.CI is failing on my PR — dig through the logs to find the root cause, then fix it and push so the pipeline re-runs until it's green.name: ci description: CI pipeline monitoring, status checks, and PR validation workflows
flowchart TD
PR([PR / Push]) --> CI{"/ci"}
CI -->|Check status| STATUS["ci:status"]:::ci
CI -->|Monitor running| MON["ci:monitoring"]:::ci
CI -->|Failed, investigate| RCACI["rca:ci"]:::rca
CI -->|Failed, fix + rerun| TDDCI["tdd:ci"]:::tdd
STATUS --> RESULT{Result?}
RESULT -->|All pass| DONE([Merge])
RESULT -->|Failed| RCACI
MON -->|Completed| STATUS
RCACI --> ROOT[Root Cause]
ROOT --> TDDCI
TDDCI -->|CI passes| DONE
classDef ci fill:#2196F3,stroke:#333,color:white
classDef rca fill:#FF5722,stroke:#333,color:white
classDef tdd fill:#4CAF50,stroke:#333,color:white
Follow this diagram as the workflow.
CI Skills
CI pipeline skills for monitoring and managing GitHub Actions workflows.
Auto-Select Sub-Skill
When this skill is invoked, determine the right sub-skill based on context:
What do you need?
│
├─ Check current PR status (what passed/failed?)
│ → Use `ci:status`
│
├─ Monitor a running CI job (wait for it to finish)
│ → Use `ci:monitoring`
│
├─ CI failed and need to investigate
│ → Use `rca:ci` (root cause analysis from logs)
│
└─ CI failed and need to fix + re-run
→ Use `tdd:ci` (commit, push, iterate)
Available Skills
| Skill | Purpose | When |
|-------|---------|------|
| ci:status | Check PR checks, failures, test results | Before/after pushing |
| ci:monitoring | Monitor running jobs, create tasks for results | After pushing, waiting |
Quick Status Check
gh pr checks
Related Skills
rca:ci- Investigate CI failurestdd:ci- Fix and re-run CI iterativelyci:status- Detailed check statusci:monitoring- Wait for running jobs
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ci-pipeline-monitoring-pr-validation-mu51ernv/download' --output '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md.part' && mv '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md.part' '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md' && test -s '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ci' && cp -R '.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv' '.claude/skills/ci'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv'openskills read 'ci-pipeline-monitoring-pr-validation-mu51ernv'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ci-pipeline-monitoring-pr-validation-mu51ernv/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.