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.
Generates Git branch names, links commits and PRs to JIRA issues, and creates PR descriptions.
/plugin marketplace add grandcamel/JIRA-Assistant-Skills/plugin install grandcamel-jira-assistant-skills@grandcamel/JIRA-Assistant-SkillsThis skill is limited to using the following tools:
docs/BEST_PRACTICES.mddocs/QUICK_START.mddocs/examples/README.mddocs/examples/github-actions-workflow.ymldocs/examples/gitlab-ci.ymldocs/examples/jenkins-pipeline.groovydocs/guides/automation-rules.mddocs/guides/branch-naming.mddocs/guides/ci-cd-integration.mddocs/guides/commit-messages.mddocs/guides/common-pitfalls.mddocs/guides/deployment-tracking.mddocs/guides/development-panel.mddocs/guides/pr-workflows.mddocs/guides/release-notes.mddocs/guides/smart-commits.mdDeveloper workflow integration for JIRA including Git, CI/CD, and release automation.
| 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
Use this skill when you need to:
Starting Development:
During Development:
Code Review:
CI/CD Integration:
Troubleshooting:
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
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 |
| 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.
# 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
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 |
| Option | Description |
|---|---|
--output, -o | Output format varies by command (see below) |
--help | Show detailed help and examples |
| 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 |
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Error (validation, API, config) |
| 2 | Invalid arguments |
See Common Pitfalls Guide for solutions to:
| 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.
| 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 |
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.