jira-dev_skill

Overview

This skill integrates developer workflows with JIRA to standardize branch names, link commits and pull requests, and generate PR descriptions. It helps teams keep development metadata in sync with JIRA for clearer traceability and smoother CI/CD automation. Use it as a safe, read-only helper for generating text and adding non-destructive links between Git activity and JIRA issues.

How this skill works

The tool inspects JIRA issue keys, issue metadata, and local commit messages to generate consistent branch names and PR descriptions. It can parse commit logs or stdin to extract issue keys, produce formatted PR templates, and call JIRA APIs to add linking metadata for commits and pull requests. Commands run via a single CLI wrapper and return text, JSON, or formatted outputs for direct use in scripts or pipelines.

When to use it

• Starting a feature, bugfix, or hotfix branch and you need a consistent branch name
• Preparing a pull request and want an issue-aware PR description or checklist
• Scanning recent commits or git logs to extract JIRA issue keys for linking
• Linking a commit or PR to a JIRA issue to populate the Development Panel
• Integrating CI/CD pipelines to auto-link builds, deployments, or PR events to issues

Best practices

• Always run commands through the provided CLI wrapper and set JIRA credentials via environment variables
• Use auto-prefix or explicit prefix flags to keep branch naming consistent across teams
• Filter parse-commits by project when processing multi-repo logs to avoid false positives
• Generate PR descriptions from the issue before pushing to ensure the PR includes testing and label context
• Prefer linking PRs and commits with metadata (status, author, repo) to maximize Development Panel visibility

Example use cases

• Generate a git checkout command for a new feature branch: jira-as dev branch-name PROJ-123 -o git
• Extract issue keys from the last 10 commits via pipe: git log --oneline -10 | jira-as dev parse-commits --from-stdin
• Produce a PR description with testing checklist and labels: jira-as dev pr-description PROJ-123 -c -l
• Link a merged pull request to an issue with status and author metadata: jira-as dev link-pr PROJ-123 -p <pr-url> -s merged -a "Jane Doe"
• Attach a commit to an issue with repository and branch context: jira-as dev link-commit PROJ-123 -c abc123def -r https://github.com/org/repo -b feature/login