run-tests

Trigger and monitor CI/CD pipelines across GitLab and GitHub Actions.

Updated Feb 13, 2026

Search Tags:#automation #testing #github actions #pipeline #gitlab #ci

One-click install

npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill run-tests-pegasus-isi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/pegasus-isi/claude-plugin-marketplace/tree/main/plugins/pegasus-dev/skills/run-tests
Command: npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill run-tests-pegasus-isi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates the manual overhead of triggering and monitoring CI pipelines, providing a unified interface to handle both GitLab CI and GitHub Actions workflows without leaving the terminal.

Core Features & Use Cases

Unified CI Control: Automatically detects whether a repository uses GitLab or GitHub Actions and applies the appropriate execution logic.
Intelligent Monitoring: Polls pipeline status and provides detailed logs for failed jobs or runs, allowing for rapid debugging of CI failures.
Use Case: When a developer pushes a new feature, they can use this skill to trigger a unit test suite on GitLab or monitor an existing GitHub Actions run, ensuring the pipeline passes before proceeding with a merge.

Quick Start

Use the run-tests skill to trigger the default unit test pipeline for the current branch.

Frequently Asked Questions about run-tests

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

FAQPage Schema

How do I trigger and monitor CI pipelines for both GitLab and GitHub Actions?▼

To trigger and monitor CI pipelines, this skill automatically detects whether a repository uses GitLab or GitHub Actions and applies the appropriate execution logic. It polls pipeline status and retrieves detailed logs for failed jobs to facilitate rapid debugging.

Can I execute unit and end-to-end tests from the terminal without leaving my environment?▼

Yes, you can execute unit and end-to-end tests by triggering the default pipeline for your current branch directly from the terminal. The skill handles execution and monitors completion status across your configured CI providers.

Do I need authenticated access and specific CLI tools to automate pipeline execution?▼

Yes, automating pipeline execution requires authenticated access to CI providers and local availability of the glab, gh, and jq CLI tools. These dependencies are necessary to trigger workflows and process pipeline traces and logs.

What's the best way to debug failing CI jobs across different CI environments?▼

The best way to debug failing CI jobs is to use the intelligent monitoring feature, which polls pipeline status and provides detailed logs for failed runs. This unified interface handles both GitLab CI and GitHub Actions workflows.

Does this tool support monitoring existing GitHub Actions runs or only triggering new pipelines?▼

This tool supports both triggering new pipelines and monitoring existing GitHub Actions runs. It polls pipeline completion status and provides detailed logs for failed jobs, ensuring the pipeline passes before proceeding with a merge.