ci-status

Show the active branch's CI pipeline status from GitLab CI or GitHub Actions.

Updated May 30, 2026
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill ci-status-alexica00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-status
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/ci-status
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill ci-status-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify at a glance the current CI pipeline status for the active branch, enabling faster decision-making before merging.

Core Features & Use Cases

  • Real-time view of GitLab CI and GitHub Actions pipelines for the active branch.
  • Supports optional MR/PR context when an argument is provided, and provides navigable URLs when CLI output is unavailable.
  • Ideal for developers to confirm pipeline health before opening a merge request.

Quick Start

Run /ci-status to display the current branch's CI pipeline status.

Frequently Asked Questions about ci-status

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

FAQPage Schema
How do I check the CI pipeline status for my current Git branch?

You can check the CI pipeline status for your current Git branch by running a command that reads local Git data and uses CLI tools to fetch real-time pipeline health for the active branch, returning status lines or navigable URLs.

Can I view GitHub Actions and GitLab CI pipeline results at a glance?

Yes, you can view GitHub Actions and GitLab CI pipeline results at a glance by relying on local Git data and the respective CLI tools to fetch the current status and construct URLs when direct CLI output is unavailable.

Do I need the glab or gh CLI installed to fetch pipeline status locally?

Yes, you need the glab or gh CLI installed locally. The process relies on these CLI tools to fetch status from GitLab CI or GitHub Actions and constructs navigable URLs when direct CLI output is unavailable for the active branch.

How can I include MR or PR context when checking CI pipeline health?

You can include MR or PR context when checking CI pipeline health by providing an argument to the command, which allows the tool to return targeted status lines or navigable URLs for the specific merge or pull request.

Why does my CI status return a URL instead of pipeline status lines?

Your CI status might return a navigable URL instead of pipeline status lines when direct CLI output is unavailable, allowing you to manually view the pipeline status in your browser for the active branch.