skills.rest
cuioss
cuiossOFFICIAL
Explore all skills by this author →
GitHub

tools-integration-ci

Detect CI provider from git remote and generate provider-specific commands.

4|Updated Jan 11, 2026
Search Tags:#automation#github#gitlab#issue#pr#ci
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill tools-integration-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tools-integration-ci
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/tools-integration-ci
Command: npx skills add https://github.com/cuioss/plan-marshall --skill tools-integration-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Unified CI operations across GitHub and GitLab to streamline PRs, CI status checks, and issue handling with a provider-agnostic API.

Core Features & Use Cases

  • Provider detection and health verification across GitHub and GitLab
  • PR operations (create, reviews, comments) and issue management
  • CI status checks and wait workflows with config-driven command resolution

Quick Start

Run the health-persist workflow to detect the provider and generate static CI commands for all operations.

Frequently Asked Questions about tools-integration-ci

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

FAQPage Schema
How do I unify CI operations for GitHub and GitLab repositories?▼

To unify CI operations for GitHub and GitLab, this tool identifies the CI provider from the git remote and generates static, provider-specific commands for PR and issue handling. It returns a structured output mapping with provider details and tool readiness.

How do I check CI status and tool availability across different git providers?▼

Checking CI status and tool availability is done by running a health verification workflow that detects the git provider and evaluates tool readiness. It generates a structured output confirming whether the required CI commands are ready to execute.

Can I manage pull requests and issues for both GitHub and GitLab using a single provider-agnostic API?▼

Yes, you can manage pull requests and issues for both GitHub and GitLab using a provider-agnostic API. It generates static commands for creating PRs, managing reviews, and handling issues tailored to the detected repository provider.

Does the CI command generation require manual configuration for each repository?▼

No, CI command generation does not require manual configuration for each repository. The tool automatically detects the provider from the repository's git remote and uses config-driven resolution to generate the appropriate static commands.

What is the output format when generating CI commands for GitHub and GitLab?▼

The output format is a structured TOON object that includes the detected provider, repository URL, tool readiness status, and the generated command mappings. It also contains structured error handling for any operational failures.

Related Skills

Explore More Software Engineering Skills→
estaciolimaestaciolima

speckit-git-remote

Extract repository owner and name from Git remote origin URLs.

Community
Basic
learnzdevelopmenthublearnzdevelopmenthub
1

dev-pr

Create GitHub pull requests and poll CI status for feature branches.

Community
Advanced
microsoft-foundrymicrosoft-foundry
56

azure-ai-fine-tuning

Automate end-to-end Azure AI Foundry fine-tuning workflows with dataset prep, training, evaluation, and deployment.

Official
Advanced
pegasus-isipegasus-isi

run-tests

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

Official
Advanced