cm-report-devops

What problem does it solve? When a pipeline is stuck due to a suspected Komodo Monitor system bug—such as missing approval tickets, approved jobs not being retried, or a stuck gate status—developers need a structured way to escalate the issue to the DevOps team without manually composing Jira service desk requests. ## Core Features & Use Cases - Guided Issue Intake: Collects pipeline URL, observed behavior, expected behavior, prior troubleshooting steps, and related CM ticket keys through a structured interview. - Automated Submission: Attempts to create a Jira work item in the DE (DevSecOps Escalated) project via acli, with an MCP Atlassian fallback when acli is unavailable or unauthenticated. - Deep-Link Fallback: Always produces a pre-filled portal deep-link and copy-paste form content so the report can be completed manually if automation fails. - Use Case: A developer notices their pipeline has been pending for 30 minutes with no approval ticket created; they run the skill, confirm the details, and a DE ticket is filed automatically with a portal link as backup. ## Quick Start Ask the assistant to report a stuck pipeline to DevOps, providing the pipeline URL and a short description of what went wrong.