mm-ci

Monitor CI/CD workflow status, list failing checks, and rerun failed jobs.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mm-ci
Source: https://github.com/mikkeymoo/claude-solo/tree/main/mm-skills/mm-ci
Command: npx skills add https://github.com/mikkeymoo/claude-solo --skill mm-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill offers quick visibility into your CI/CD workflows and enables management tasks such as retrying failing runs and viewing logs without leaving the terminal.

Core Features & Use Cases

  • Current CI/CD Runs: Provides an overview of the latest runs, including status and summary.
  • Failing Checks: Lists only failing checks with concise error summaries.
  • Retry Failed Workflows: Enables requeuing specific failed workflow runs.
  • Stream Logs: Allows viewing logs from specific workflow runs.
  • Use Case: Quickly identify issues in your CI/CD pipeline, address failures, and get the necessary information to make informed decisions.

Quick Start

Check the status of your current CI/CD runs using the command /mm-ci --status.

Frequently Asked Questions about mm-ci

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

FAQPage Schema
How do I check CI/CD workflow status from the terminal?

You can check CI/CD workflow status from the terminal by running a command like `/mm-ci --status`, which provides an overview of the latest runs including their current status and summary.

How do I view error logs for failing CI checks without leaving the terminal?

To view error logs for failing CI checks, you can use the Skill to list only failing checks with concise error summaries and stream logs from specific workflow runs directly in your terminal.

Can I rerun failed CI jobs using the gh CLI?

Yes, you can rerun failed CI jobs using the gh CLI by triggering the Skill's retry mechanism, which enables requeuing specific failed workflow runs without navigating to a web interface.

What is the best way to monitor CI/CD pipelines for failures?

The best way to monitor CI/CD pipelines for failures is using a terminal-based management tool that lists failing checks, displays concise error summaries, and allows you to rerun failed workflows quickly.

Do I need gh installed to manage GitHub Actions workflows from the terminal?

Yes, you need the `gh` dependency installed, as the Skill relies on this CLI component to interact with your repository and manage CI/CD workflow statuses, logs, and retries.

Why does my CI workflow keep failing and how can I quickly identify the issue?

Your CI workflow may fail due to check errors, which you can quickly identify by listing failing checks to view concise error summaries and streaming the specific logs of the failed run.