🎯

jira-workflow

🎯Skill

from bitsoex/bitso-java

VibeIndex|
What it does

jira-workflow skill from bitsoex/bitso-java

πŸ“¦

Part of

bitsoex/bitso-java(32 items)

jira-workflow

Installation

πŸ“‹ No install commands found in docs. Showing default command. Check GitHub for actual instructions.
Quick InstallInstall with npx
npx skills add bitsoex/bitso-java --skill jira-workflow
7Installs
35
-
Last UpdatedJan 26, 2026

Skill Details

SKILL.md

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

Overview

# 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

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

Skill Contents

Sections

  • [Core Principles](#core-principles) (L24-L31)
  • [Workflow Overview](#workflow-overview) (L56-L65)
  • [Quick Reference](#quick-reference) (L66-L100)
  • [References](#references) (L101-L110)
  • [Severity-Based Processing](#severity-based-processing) (L111-L127)
  • [Best Practices](#best-practices) (L128-L135)
  • [Skill Dependencies](#skill-dependencies) (L136-L141)
  • [Related](#related) (L142-L145)

Available Resources

πŸ“š references/ - Detailed documentation

  • [branch naming](references/branch-naming.md)
  • [project discovery](references/project-discovery.md)
  • [severity processing](references/severity-processing.md)
  • [ticket creation](references/ticket-creation.md)
  • [ticket search](references/ticket-search.md)

---

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

```text

πŸ€–πŸ›‘οΈ 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

```text

{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

  1. CRITICAL - Fix first
  2. HIGH - Only after no CRITICAL remain
  3. MEDIUM/MODERATE - Only after no HIGH remain
  4. LOW - Only after no MEDIUM remain

SonarQube Severity Order

  1. BLOCKER - Fix first
  2. CRITICAL - Only after no BLOCKER remain
  3. MAJOR - Only after no CRITICAL remain
  4. MINOR - Only after no MAJOR remain
  5. INFO - Only after no MINOR remain

Best Practices

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

Skill Dependencies

| Skill | Purpose |

|-------|---------|

| pr-lifecycle | PR creation, commit formats, GitHub CLI |

Related

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