From atlassian-suite
This skill should be used when the user asks to "link this PR to a jira issue", "link pr to jira", "associate PR with ticket", "add Jira link to PR", or runs `/atlassian-suite:link-pr-to-issue`. Establishes a bidirectional link between a Bitbucket pull request and a Jira issue (issue gets a remote link to the PR; PR description and branch reference the issue key).
npx claudepluginhub acendas/acendas-marketplace --plugin atlassian-suiteThis skill is limited to using the following tools:
Create a bidirectional link between a pull request and a Jira issue.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Create a bidirectional link between a pull request and a Jira issue.
$1 = PR identifier (full URL like https://bitbucket.org/<ws>/<repo>/pull-requests/123, or <repo>/123).
$2 = Optional Jira issue key (e.g. PROJ-456). If omitted, infer from the PR branch name or title.
Resolve the PR. Parse $1 into (workspace, repo_slug, pr_id). Call mcp__acendas-atlassian__get_pull_request to fetch title, source branch, description, author, and current state.
Resolve the Jira issue.
$2 is provided, call mcp__acendas-atlassian__jira_get_issue to validate.feature/PROJ-456-something) and PR title for an issue key matching [A-Z][A-Z0-9]+-\d+.Update the Jira side. Add a remote link via mcp__acendas-atlassian__jira_create_remote_issue_link with:
url = PR HTML URLtitle = [<repo>] PR #<id>: <PR title>icon_url = Bitbucket favicon (or omit)relationship = "implements" or "fixes" based on user intent (default: implements).Optionally add a comment via mcp__acendas-atlassian__jira_add_comment summarizing the PR (1 line: title + author + source→destination branches).
Update the PR side. If the PR description does not already contain the issue key, call mcp__acendas-atlassian__update_pull_request to prepend Jira: <ISSUE-KEY> to the description. If the PR is read-only or update fails, fall back to posting a comment via mcp__acendas-atlassian__add_pull_request_comment containing the issue link.
Report. Summarize what changed in 2 short lines: which Jira link was created, which PR field was updated.
READ_ONLY_MODE=true), skip writes and report what would have changed.