jira-cve

Create Jira security tickets from GitHub Dependabot alert URLs.

3|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-cve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-cve
Source: https://github.com/dimagi/dimagi-claude-workflows/tree/main/plugins/commcare-tech/skills/jira-cve
Command: npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-cve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically convert GitHub Dependabot security alerts into formal Jira tickets to ensure timely remediation and consistent tracking across projects.

Core Features & Use Cases

  • Fetch and parse Dependabot alert data from a given URL
  • Map vulnerability details (package, ecosystem, severity, CVE, patched version) into Jira fields
  • Create or update a security ticket in the SAAS project with standardized format
  • Ensure traceability by including the original Dependabot alert URL in the ticket description

Quick Start

Provide a Dependabot alert URL and let the skill create a Jira CVE ticket.

Frequently Asked Questions about jira-cve

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

FAQPage Schema
How do I create Jira tickets from GitHub Dependabot alerts?

You can create Jira tickets from Dependabot alerts by fetching alert details from the URL and mapping vulnerability data like package, severity, and patched version into standardized security tickets.

What information is needed to convert a Dependabot alert into a Jira CVE ticket?

Converting a Dependabot alert into a Jira CVE ticket requires the Dependabot alert URL to fetch and parse vulnerability details, alongside valid Jira SAAS project settings for priority and sprint assignment.

How does mapping Dependabot vulnerability details to Jira fields work?

Mapping Dependabot vulnerability details to Jira fields works by parsing the alert URL to extract the package, ecosystem, severity, CVE, and patched version, then enforcing these into standardized Jira ticket fields.

Can I use this to track CVEs and mitigations in Jira SAAS projects?

Yes, you can use this to track CVEs and mitigations in Jira SAAS projects, as it enforces field mappings and delegates ticket creation with proper project, priority, and sprint settings for security remediation.

Does creating Jira security tickets from Dependabot alerts include the original alert URL?

Yes, creating Jira security tickets from Dependabot alerts includes the original alert URL directly in the ticket description to ensure complete traceability back to the GitHub source.