Verified:GitHub

cm-devops-fix

Diagnoses and remediates blocked deployment-gate pipelines across GitLab, Komodo Monitor, and Jira.

Updated Jul 22, 2026

Search Tags:#devops #root cause analysis #jira #gitlab #change management #deployment gate #pipeline debugging

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cm-devops-fix-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cm-devops-fix
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/change-management/skills/cm-devops-fix
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cm-devops-fix-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a GitLab pipeline is blocked by the Komodo Monitor change-management deployment gate, engineers struggle to tell whether the cause is a genuine pending approval, a system outage, a missed webhook, or a misconfiguration. This Skill runs a systematic diagnostic to pinpoint the root cause and offers safe, confirmed fixes. ## Core Features & Use Cases - Systematic Gate Diagnosis: Fetches pipeline state, job statuses, and the deployment-gate commit status via GitLab MCP tools or glab CLI fallbacks. - Multi-System Health Checks: Verifies Komodo Monitor reachability, webhook delivery, Jira automation rules, and pre-approval CSV/coverage configuration. - Confirmed Remediation: Offers fixes such as retrying cancelled jobs, re-triggering webhooks, updating the pre-approved projects CSV, or emergency gate override — each requiring explicit user confirmation. - Use Case: A DevOps engineer sees a pipeline stuck with a 'running' gate status for 30 minutes and no CM ticket. They run the skill with the pipeline URL, which identifies that the Jira automation rule failed to create the ticket and recommends re-triggering the webhook. ## Quick Start Run /change-management:cm-devops-fix with a blocked pipeline URL, job URL, or CM ticket key to diagnose why the deployment gate is not proceeding.

Frequently Asked Questions about cm-devops-fix

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

FAQPage Schema

How do I diagnose a GitLab pipeline blocked by a deployment gate?▼

Provide the blocked pipeline URL, job URL, or CM ticket key to the skill. It fetches pipeline details, job statuses, and the gate commit status, then checks Komodo health, webhook delivery, and Jira automation to produce a structured root cause summary.

Why is my pipeline stuck with no change management ticket created?▼

A gate status stuck in 'running' for over two minutes with no CM ticket usually means the Jira automation rule failed or the major-change analysis hung. The skill searches recent CM tickets and directs you to check the Jira Automation rule execution logs.

Can the skill retry cancelled GitLab jobs after approval?▼

Yes. When a CM ticket is approved but jobs were not automatically retried, the skill offers to retry cancelled jobs via glab ci retry or the GitLab API, but only after you explicitly confirm the action.

How does pre-approval work for the deployment gate?▼

Pre-approved projects are listed in a CSV in the change-management repo, which Komodo syncs into its database on a configurable schedule. Pre-approval also requires over 75% coverage recorded in Komodo's project_coverage_summary table.

When should I manually override the deployment gate status?▼

Manual override is an emergency-only option for when Komodo itself is broken and cannot process approvals, and the change has been approved through another channel. The skill requires explicit confirmation before setting the gate status to success.