jira-integration_skill

This skill creates and manages Jira tickets, discovers projects, searches existing issues, and links work across branches and PRs for efficient remediation.

JavaScript

35

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bitsoex/bitso-java --skill jira-integration

SKILL.md5.0 KB

Overview

This skill automates creating and managing Jira tickets for AI-driven code work, enforcing severity-based processing and clear traceability. It discovers the correct Jira project, searches for existing tickets, creates new tickets when needed, and generates branch names tied to Jira keys. The goal is to keep fixes reviewable, linked, and prioritized by severity.

How this skill works

The skill first discovers the user's Jira project key instead of relying on hardcoded values. It searches for open tickets that match the issue context; if none exist it creates a new ticket using standardized summaries and metadata. It then suggests branch names that include the Jira key and enforces processing one severity level at a time, linking commits and PRs back to the ticket.

When to use it

When fixing vulnerabilities or Dependabot alerts and you must track work in Jira
When resolving SonarQube or code-quality issues that need prioritized handling
When improving test coverage and you need traceable, reviewable PRs
When creating automated commits so each change is linked to a ticket
When you want consistent branch naming and ticket-to-commit traceability

Best practices

Always discover the project key programmatically; never hardcode it
Search for existing tickets first and avoid duplicate tickets
Process issues one severity level per PR to keep changes focused
Use emoji and standardized ticket summaries to make intent clear
Link Jira ticket ↔ branch ↔ commits ↔ PR and update ticket status as work progresses

Example use cases

Create a Jira ticket and branch for CRITICAL security fixes, then open a PR with linked commits
Search for existing SonarQube blocker tickets and batch related fixes into a single reviewable PR
Generate a test/PROJECT-123-coverage branch and open a ticket when adding unit tests to a module
Update dependency versions with a chore/PROJECT-456 branch and a descriptive Jira ticket
Run automated remediation for MEDIUM issues only after HIGH and CRITICAL issues have been addressed

FAQ

The skill will attach work to the existing ticket instead of creating a duplicate and will use that ticket key in the branch name.

How does severity-based processing work?

Issues are processed in a defined order (e.g., CRITICAL before HIGH) and the skill will not proceed to a lower severity until higher severities are cleared.