Verified:GitHub

cm-diagnose

Diagnoses blocked GitLab CI/CD pipelines held by the change-management deployment gate.

Updated Jul 22, 2026

Search Tags:#pipeline #jira #gitlab #ci-cd #diagnose #change-management #deployment-gate

One-click install

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

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cm-diagnose
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/change-management/skills/cm-diagnose
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cm-diagnose-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 Trigent change-management gate (Komodo Monitor), developers often cannot tell whether the block is a genuine pending approval, a still-running analysis, or a system bug. This Skill fetches the gate status, classifies the block, and tells you the exact next action — read-only, without modifying anything. ## Core Features & Use Cases - Gate Status Retrieval: Accepts a pipeline, job, or merge request URL and fetches the `Change Management - Deployment Gate` commit status via GitLab MCP tools or the `glab` CLI fallback. - Block Classification: Distinguishes between grace-period analysis, genuine pending approval (with CM Jira ticket lookup), system bugs (hung analysis or failed ticket creation), rejections, and pre-approved/urgent-bypass passes. - Degraded-Mode Handling: Probes Jira connectivity via `acli` first, then Atlassian MCP, and degrades gracefully with a warning banner when the CM service-desk project is unreachable. - Use Case: A developer pastes a stuck production pipeline URL and learns that a CM Jira ticket CM-123 is awaiting approval, that the pipeline will auto-resume on approval, and how to use the urgent bypass only for genuine emergencies. ## Quick Start Run /change-management:cm-diagnose followed by your blocked GitLab pipeline, job, or merge request URL to get a diagnosis and next action.

Frequently Asked Questions about cm-diagnose

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

FAQPage Schema

How do I find out why my GitLab pipeline is blocked?▼

Paste the pipeline, job, or merge request URL into the cm-diagnose command. It fetches the Change Management - Deployment Gate commit status, classifies the block, and returns a verdict with the single recommended next action.

How do I check a change management gate status in GitLab CI?▼

The gate appears as a commit status named Change Management - Deployment Gate on the pipeline's commit SHA. This Skill retrieves it via GitLab MCP tools, with a glab api fallback, and interprets its state and description for you.

What does it mean when the deployment gate says pending approval?▼

It means a CM Jira ticket was automatically created and is waiting for human approval, which is expected behavior. The pipeline resumes automatically once approved; the Skill can locate the ticket key and status when Jira is reachable.

Can I bypass the change management gate for urgent deployments?▼

Yes, set the pipeline variable isUrgentChange to true when re-running the pipeline, or include urgent, hotfix, or emergency in the branch name. This should only be used for genuine emergencies per team policy.

Why is my pipeline stuck in analysis past the grace period?▼

If the gate description still shows analysis in progress well beyond the 2-minute grace period, Komodo Monitor likely hung or its Jira automation failed. The Skill flags this as a system bug and offers to file a DevOps report.

Does cm-diagnose work without Jira access?▼

Yes, it degrades gracefully. Without acli or Atlassian MCP access to the CM service-desk project, it diagnoses from GitLab gate signals only, shows a degraded-mode banner, and lowers classification confidence accordingly.