cm-request-change

Submits manual major or urgent change requests to a Jira service desk portal.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cm-request-change-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-request-change
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/change-management/skills/cm-request-change
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cm-request-change-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual infrastructure or configuration changes that bypass the GitLab CI/CD pipeline still require formal change approval, and this Skill guides you through gathering the required details and submitting a change request to the Jira service desk (portal 3) without leaving your workflow. ## Core Features & Use Cases - Structured Intake: Walks through a questionnaire covering change title, type (Major/Urgent), justification, rollback plan, and risk assessment before submission. - Multi-Path Submission: Attempts automated submission via the servicedeskapi REST endpoint with curl, falls back to the Atlassian MCP tool, and always provides a pre-filled portal deep-link. - Use Case: During a production incident, you need an emergency Redis cluster restart on prod AKS. Run the skill, answer the prompts, and get a CM ticket created (or a pre-filled portal link) plus guidance to notify approvers immediately. ## Quick Start Ask the assistant to request an urgent manual change to restart the Redis cluster in the production AKS environment.

Frequently Asked Questions about cm-request-change

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

FAQPage Schema
How do I request a manual change that bypasses the GitLab pipeline?

Run the cm-request-change skill and answer the intake questions about the change title, type, justification, rollback plan, and risk. It submits the request to Jira service desk portal 3 via the REST API or provides a pre-filled portal link.

How do I submit an emergency change request to Jira service desk?

Provide the change description and incident details when prompted, marking the change as Urgent. The skill composes a summary with current impact and severity, then submits via curl to the servicedeskapi endpoint or gives you a portal deep-link to complete manually.

Does acli support Jira service desk portal requests?

No, acli v1.3.x has no servicedesk subcommand and cannot create portal 3 requests. The skill uses curl against the servicedeskapi REST endpoint with JIRA_EMAIL and JIRA_TOKEN, or falls back to the MCP Atlassian tool.

When should I not use the manual change request skill?

Do not use it when a GitLab pipeline is blocked by the Komodo Monitor gate; use the cm-diagnose skill instead. This skill is only for changes that do not go through GitLab CI/CD at all, such as direct infrastructure or configuration changes.

What credentials are needed for automated Jira change request submission?

Automated submission requires the JIRA_EMAIL and JIRA_TOKEN environment variables for the servicedeskapi REST endpoint. If they are not set, the skill falls back to the MCP Atlassian tool or a pre-filled portal deep-link.