Jira Workflow

jira-workflow

Jira ticket creation and management for AI agent commands, with severity-based processing and proper integration

majiayu000/claude-skill-registry-data·0installs23starsSecurity

SKILL.md

Full skill instructions

Jira Workflow

Best practices for AI agents to create and manage Jira tickets when performing automated work like fixing vulnerabilities, resolving SonarQube issues, or improving test coverage.

Core Principles

Create Ticket Before Work - Always create/find a Jira ticket before starting
Discover Project Key - Never hardcode project keys
Search Before Creating - Check for existing tickets first
Severity-Based Processing - Process issues one severity level at a time
Link Everything - Connect Jira → Branch → Commits → PR

Skill Contents

Sections

Core Principles (L24-L31)
Workflow Overview (L56-L65)
Quick Reference (L66-L100)
References (L101-L110)
Severity-Based Processing (L111-L127)
Best Practices (L128-L135)
Skill Dependencies (L136-L141)
Related (L142-L145)

Available Resources

📚 references/ - Detailed documentation

Workflow Overview

Step	Description	Reference
0. Discover	Find user's Jira project key	`references/project-discovery.md`
1. Search	Check for existing open tickets	`references/ticket-search.md`
2. Create	Create ticket if none exists	`references/ticket-creation.md`
3. Branch	Create branch with Jira key	`references/branch-naming.md`
4. Process	Fix by severity level	`references/severity-processing.md`

Quick Reference

Emoji Conventions

Work Type	Emoji	Example
AI-assisted (all)	🤖	Required in ALL AI commits/PRs
Security/Vulnerability	🛡️	`🤖 🛡️ fix(security): resolve critical CVE`
Code Quality/SonarQube	✅	`🤖 ✅ fix(quality): resolve BLOCKER issues`
Test Coverage	🧪	`🤖 🧪 test: improve coverage`
Dependency Updates	📦	`🤖 📦 chore(deps): update Spring Boot`
Documentation	📝	`🤖 📝 docs: update API documentation`
Performance	⚡	`🤖 ⚡ perf: optimize queries`
Refactoring	♻️	`🤖 ♻️ refactor: simplify error handling`

Ticket Summary Format

🤖🛡️ Fix [SEVERITY] Dependabot vulnerabilities in [repo-name]
🤖✅ Resolve [SEVERITY] SonarQube issues in [repo-name]
🤖🧪 Improve test coverage for [module/class]
🤖📦 Update [dependency] to [version]

Branch Naming

{type}/{JIRA-KEY}-{short-description}

Examples:

fix/PROJ-123-critical-vulnerabilities
fix/PROJ-456-blocker-sonar-issues
test/PROJ-789-coverage-payment-service

References

Reference	Content
`references/project-discovery.md`	How to discover user's Jira project key
`references/ticket-search.md`	JQL queries to find existing tickets
`references/ticket-creation.md`	Create tickets with proper format
`references/branch-naming.md`	Branch naming with Jira keys
`references/severity-processing.md`	Process by severity level

Severity-Based Processing

Vulnerability Severity Order

CRITICAL - Fix first
HIGH - Only after no CRITICAL remain
MEDIUM/MODERATE - Only after no HIGH remain
LOW - Only after no MEDIUM remain

SonarQube Severity Order

BLOCKER - Fix first
CRITICAL - Only after no BLOCKER remain
MAJOR - Only after no CRITICAL remain
MINOR - Only after no MAJOR remain
INFO - Only after no MINOR remain

Best Practices

One severity per PR - Keep PRs focused and reviewable
Batch related fixes - Group similar issues in one commit
Clear descriptions - Document what was fixed and why
Link everything - Jira ticket ↔ Branch ↔ Commits ↔ PR
Update ticket status - Move ticket through workflow as work progresses

Skill Dependencies

Skill	Purpose
`pr-lifecycle`	PR creation, commit formats, GitHub CLI

.claude/skills/pr-lifecycle - PR creation and management
.claude/skills/stacked-prs - Stacked PR workflows

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/majiayu000/claude-skill-registry-data --skill jira-workflow

View on GitHub

data/jira-workflow/SKILL.md

More Security skills

View all

Security

supabase

Handles the full Supabase workflow from schema changes to deployment, with built-in security guardrails that catch common traps like RLS...

2.7K 308.9K

View

Security

neon-postgres

Comprehensive guides and best practices for Neon Serverless Postgres, covering setup, connection methods, authentication, and platform APIs.

98 216.2K

View

Security

firebase-auth-basics

Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.

462 163.8K

View

Security

firebase-security-rules-auditor

A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.

462 127.7K

View

Security

firebase-ai-logic-basics

Official skill for integrating Firebase AI Logic (Gemini API) into web applications. Covers setup, multimodal inference, structured output, and security.

462 125.1K

View

Security

better-auth-best-practices

Complete Better Auth server and client setup with database adapters, session management, plugins, and security configuration.

222 118.2K

View

Security

vercel-cli-with-tokens

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

31.9K 116.1K

View

Security

cloudflare

Complete Cloudflare platform integration with decision trees for compute, storage, AI, networking, security, and infrastructure-as-code.

3K 110.7K

View

Security

azure-compliance

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

253 103K

View