shield_lock
金大哥
← 返回 Skill 列表
extension
分类: 开发与工程无需 API Key

"jira-developer-integration"

Git和开发人员工作流程集成。触发器：'生成分支名称'，'创建分支名称'，'为...创建分支名称'，'编写PR描述'，'为...编写PR描述'，'链接PR'，'链接拉取请求'，'解析提交'，'从提交中提取问题'，'智能提交'，'开发面板'。用于与JIRA集成的Git、GitHub、GitLab、Bitbucket。不适用于：问题字段更新（使用jira-issue），搜索问题（使用jira-search），状态转换（使用jira-lifecycle）。

person作者: jakexiaohubgithub
open_in_new仓库download下载资源包

JIRA Developer Integration Skill

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

Risk Levels

| Operation | Risk | Notes | |-----------|------|-------| | Generate branch name | - | Read-only, local output | | Parse commits | - | Read-only, local analysis | | Get commits | - | Read-only | | Generate PR description | - | Read-only, local output | | Link commit | - | Adds metadata, easily removed | | Link PR | - | Adds metadata, easily removed |

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.

| Command | Description | |---------|-------------| | jira-as dev branch-name | Generate consistent branch names from issues | | jira-as dev parse-commits | Extract issue keys from commit messages | | jira-as dev link-commit | Link commits to JIRA issues | | jira-as dev get-commits | Retrieve development information | | jira-as dev link-pr | Automatically link PRs to JIRA | | jira-as dev pr-description | Generate PR descriptions from issues |

Recommended Starting Points

| Role | Start With | |------|------------| | Developer | jira-as dev branch-name PROJ-123 | | Git Administrator | Branch names, then PR integration | | DevOps Engineer | CI/CD integration with link-pr and link-commit | | Release Manager | Deployment tracking with link-pr |

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

Quick Examples

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

# Generate branch name with explicit prefix (-p is short for --prefix)
# Valid prefixes: feature, bugfix, hotfix, task, epic, spike, chore, docs
jira-as dev branch-name PROJ-123 -p bugfix
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 (-o is short for --output)
jira-as dev branch-name PROJ-123 -o 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 (-p is short for --project)
jira-as dev parse-commits "Fix PROJ-123 and OTHER-456" -p PROJ

# Generate PR description with testing checklist (-c is short for --include-checklist)
jira-as dev pr-description PROJ-123 -c
jira-as dev pr-description PROJ-123 --include-checklist

# Generate PR description with labels (-l is short for --include-labels)
jira-as dev pr-description PROJ-123 -l --include-components

# Generate PR description and copy to clipboard
jira-as dev pr-description PROJ-123 --copy

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

# Link PR with title (-t is short for --title)
jira-as dev link-pr PROJ-123 -p https://github.com/org/repo/pull/456 -t "Fix authentication bug"

# Link PR with status and author (-s, -a are short forms)
jira-as dev link-pr PROJ-123 -p https://github.com/org/repo/pull/456 -s merged -a "Jane Doe"

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

# Link commit with additional metadata (-a for --author, -b for --branch)
jira-as dev link-commit PROJ-123 -c abc123def -a "John Doe" -b 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 (-o is short for --output)
jira-as dev get-commits PROJ-123 --repo "org/repo" -o table

Configuration

Requires JIRA credentials via environment variables:

| Setting | Description | |---------|-------------| | JIRA_SITE_URL | Your JIRA instance URL | | JIRA_EMAIL | Your JIRA email | | JIRA_API_TOKEN | Your JIRA API token |

Common Options

| Option | Description | |--------|-------------| | --output, -o | Output format varies by command (see below) | | --help | Show detailed help and examples |

Output Formats by Command

| Command | Available Formats | |---------|------------------| | branch-name | text, json, git | | parse-commits | text, json, csv | | pr-description | text, json | | link-commit | text, json | | link-pr | text, json | | get-commits | text, json, table |

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | Error (validation, API, config) | | 2 | Usage error (invalid arguments); also used for authentication errors |

Troubleshooting

See Common Pitfalls Guide for solutions to:

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

Advanced Topics

| Topic | Guide | |-------|-------| | Branch naming conventions | Branch Naming | | Commit message formats | Commit Messages | | Smart Commits | Smart Commits | | PR workflows | PR Workflows | | Development Panel | Development Panel | | CI/CD integration | CI/CD Integration | | Automation rules | Automation Rules | | Deployment tracking | Deployment Tracking | | Release notes | Release Notes |

For comprehensive guidance, see Best Practices Guide.

Related Skills

| Skill | Relationship | |-------|-------------| | jira-issue | Get issue details for branch names | | jira-lifecycle | Auto-transition on PR merge | | jira-collaborate | Commit linking uses comments | | jira-search | Find issues for bulk operations | | jira-bulk | Process multiple issues from commits |