From atlassian-suite
This skill should be used when the user asks to "triage this issue", "triage the bug", "categorize this jira ticket", "find related docs and prs for this issue", or runs `/atlassian-suite:triage-issue`. Pulls related Confluence docs and Bitbucket PRs/commits for a Jira issue, suggests labels/priority/component, and proposes a transition.
npx claudepluginhub acendas/acendas-marketplace --plugin atlassian-suiteThis skill is limited to using the following tools:
Enrich a Jira issue with related context and propose a triage action.
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.
Enrich a Jira issue with related context and propose a triage action.
$1 = Jira issue key (e.g. PROJ-456).
Load the issue. Call mcp__acendas-atlassian__jira_get_issue. Capture summary, description, current status, type, priority, labels, components, assignee.
Find related context in parallel:
mcp__acendas-atlassian__jira_search with JQL project = {project} AND text ~ "{key-terms-from-summary}" AND key != {issue-key} (limit 5). Key terms = top 3 nouns from summary.mcp__acendas-atlassian__confluence_search with CQL text ~ "{key-terms}" (limit 5).mcp__acendas-atlassian__list_pull_requests searching by query {issue-key} if the API supports it; otherwise list recent PRs and grep their titles/descriptions for {issue-key}.mcp__acendas-atlassian__jira_get_transitions.Analyze:
prod down, customer impact, data loss, suggest Highest or Critical. If nice to have, cleanup, suggest Low. Otherwise leave as-is.Open/To Do and a related PR exists in OPEN state → suggest In Progress. If status is In Review and a related PR is MERGED → suggest Done.Render the brief:
{ISSUE-KEY} — {summary}
Status: {current} → suggested: {proposed}
Type: {type} Priority: {current} → suggested: {proposed}
Labels: {current} → suggested: +{add} -{remove}
Component: {current} → suggested: {proposed}
Related issues:
- {KEY}: {summary} ({status})
Related Confluence:
- {title} — {url}
Related PRs:
- PR #{id}: {title} ({state})
Possible duplicates:
- {KEY} — {similarity reason}
Suggested next action:
- Transition to {status}
- Add labels: {labels}
- Assign to: {user (if obvious from PR author)}
Offer to apply. Ask the user to confirm any subset of the proposed changes. Only apply on explicit yes (use jira_update_issue and jira_transition_issue). Default action: report only.
No related context found for that section.