---

name: "jira-developer-integration" description: "Developer workflow integration for JIRA - Git branch names, commit parsing, PR descriptions. Use when generating branch names from issues, linking commits, or creating PR descriptions. Also use to troubleshoot Development Panel issues or automate CI/CD integration." version: "1.0.0" author: "jira-assistant-skills" license: "MIT" allowed-tools: ["Bash", "Read", "Glob", "Grep"]

JIRA Developer Integration Skill

Developer workflow integration for JIRA including Git, CI/CD, and release automation.

Risk Levels

Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible

Quick Start: Get started in 10 minutes

When to Use This Skill

Use this skill when you need to:

Starting Development:

• Generate standardized Git branch names from JIRA issues
• Create feature, bugfix, or hotfix branches with consistent naming

During Development:

• Extract JIRA issue keys from commit messages
• Link Git commits to JIRA issues via comments
• Log time and transition issues from commits (Smart Commits)

Code Review:

• Generate PR descriptions from JIRA issue details
• Link Pull Requests (GitHub, GitLab, Bitbucket) to JIRA issues

CI/CD Integration:

• Track builds and deployments in JIRA
• Auto-transition issues based on PR/deployment events
• Generate release notes from JIRA versions

Troubleshooting:

• Debug why Development Panel shows empty
• Fix Smart Commits not working
• Resolve PR linking issues

IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.

Available Commands

All commands support --help for full documentation.

Recommended Starting Points

Advanced: See CI/CD Integration Guide for pipeline setup.

Quick Examples

Copy# Generate branch name with default prefix (feature)
jira-as dev branch-name PROJ-123

# Generate branch name with explicit prefix
jira-as dev branch-name PROJ-123 --prefix bugfix

# Auto-detect prefix from issue type (Bug -> bugfix, Story -> feature, etc.)
jira-as dev branch-name PROJ-123 --auto-prefix

# Output git checkout command directly
jira-as dev branch-name PROJ-123 --output git

# Extract issues from a single commit message
jira-as dev parse-commits "feat(PROJ-123): add login"

# Extract issues from git log via pipe
git log --oneline -10 | jira-as dev parse-commits --from-stdin

# Filter to specific project
jira-as dev parse-commits "Fix PROJ-123 and OTHER-456" --project PROJ

# Generate PR description with testing checklist
jira-as dev pr-description PROJ-123 --include-checklist

# Generate PR description with labels and components
jira-as dev pr-description PROJ-123 --include-labels --include-components

# Link PR to issue (--pr is required)
jira-as dev link-pr PROJ-123 --pr https://github.com/org/repo/pull/456

# Link PR with status and author
jira-as dev link-pr PROJ-123 --pr https://github.com/org/repo/pull/456 --status merged --author "Jane Doe"

# Link commit to issue (--commit is required)
jira-as dev link-commit PROJ-123 --commit abc123def --message "feat: add login" --repo https://github.com/org/repo

# Link commit with additional metadata
jira-as dev link-commit PROJ-123 --commit abc123def --author "John Doe" --branch feature/login

# Get commits linked to issue
jira-as dev get-commits PROJ-123

# Get commits with detailed information
jira-as dev get-commits PROJ-123 --detailed

# Get commits filtered by repository
jira-as dev get-commits PROJ-123 --repo "org/repo" --output table

Configuration

Requires JIRA credentials via environment variables:

Common Options

Output Formats by Command

Exit Codes

Troubleshooting

See Common Pitfalls Guide for solutions to:

• Development Panel showing empty
• Smart Commits not working
• PR linking issues
• Branch name problems

Advanced Topics

For comprehensive guidance, see Best Practices Guide.

Related Skills