From atlassian-suite
This skill should be used when the user asks to "post pr summary to jira", "summarize this pr in jira", "comment pr status on jira issue", or runs `/atlassian-suite:pr-summary-to-jira`. Generates a concise PR status summary and posts it as a Jira comment on the linked issue, keeping non-technical stakeholders updated without leaving Jira.
npx claudepluginhub acendas/acendas-marketplace --plugin atlassian-suiteThis skill is limited to using the following tools:
Generate a stakeholder-friendly PR status summary and post it as a Jira comment.
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.
Generate a stakeholder-friendly PR status summary and post it as a Jira comment.
$1 = PR identifier. $2 = Optional Jira issue key (auto-detected from branch/title if omitted; see link-pr-to-issue skill for resolution rules).
Fetch PR data in parallel:
mcp__acendas-atlassian__get_pull_request — title, state, author, reviewers, branches, merge statusmcp__acendas-atlassian__get_pull_request_diffstat — files changed + line countsmcp__acendas-atlassian__get_pull_request_activity — approvals, change requests, comment countCompose the summary. Use Atlassian wiki markup for Jira:
*PR #{id}: {title}*
Author: {author} | Reviewers: {reviewer-count} ({approved}/{requested-changes}/{pending})
Branches: {source} → {destination}
Diff: {files-changed} files (+{added} / -{deleted})
Status: {state} {merge-status-suffix}
{pr-url}
OPEN — ready for review, OPEN — 2 changes requested, MERGED on YYYY-MM-DD, DECLINED.Post the comment. Call mcp__acendas-atlassian__jira_add_comment against the resolved issue key.
Report. Print one line: Posted PR summary to <ISSUE-KEY>: <jira-comment-url>.
jira_get_issue returns recent comments) and check for an existing comment starting with *PR #{id}:. If found, ask the user whether to skip or post a fresh summary.MERGED state, also suggest a transition (e.g. "Mark issue as Done?") but do not transition without explicit user approval.