From jira
Add comments, feedback, review notes, or replies to existing JIRA issues. Use when the user wants to post a comment, reply to a discussion, leave review feedback, or add notes on a JIRA ticket. Transforms raw input into clear, well-structured comments. Also use when the user wants to post code review findings or PR review results to a JIRA ticket. Triggers on any request to comment on, reply to, or add feedback to a JIRA issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:jira-feedbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add comments and feedback to existing JIRA issues. Transforms raw input into clear, well-structured comments.
Add comments and feedback to existing JIRA issues. Transforms raw input into clear, well-structured comments.
AskUserQuestion (see below)$ARGUMENTS as the feedback content; if a JIRA issue key is present, extract itcloudId (see below)Before anything else, use AskUserQuestion with two questions:
Use the selected language for the entire draft.
Treat the entire $ARGUMENTS as the feedback content. Scan for a JIRA issue key matching [A-Z]{2,6}-\d+ — if found, extract it for use in Step 3 and Step 7.
The issue key is optional. If no key is present, skip Step 3 and ask for the issue key later in Step 7 (before sending).
Examples:
TES-1234 I think the API regression also happens on staging → key: TES-1234, content: the full textthere are five things wrong with the export feature → no key, content: the full textPR Review format — additional parsing:
When PR Review format is selected, determine the input source. The expected input is a triage report (output of the triage skill, with Fix Now / Fix Later / Skip groups), but raw review reports also work as a fallback.
$ARGUMENTS contains a file path (matches *.md or a recognizable path like docs/reviews/...) — read the file. If it contains Fix Now / Fix Later / Skip sections, treat it as a triage report. If it contains Action Items / Findings by severity, treat it as a raw review report.$ARGUMENTS contains reviewer-prefixed IDs (VM-, BE-, FE-, QA-, SC-, DV- followed by digits) — parse as pasted review findingsAskUserQuestion (header: "Review source") to provide the triage/review report path or paste the findingsStill extract a JIRA issue key if present (same as above).
Examples:
TES-1234 docs/reviews/feature-auth-2026-03-15-triage.md → key: TES-1234, source: triage fileTES-1234 docs/reviews/feature-auth-2026-03-15.md → key: TES-1234, source: raw review fileTES-1234 BE-001 N+1 query in settings loader Critical ... → key: TES-1234, source: pasted findingsIf an issue key was found in Step 2, use the getJiraIssue MCP tool to fetch the issue:
Read the issue summary, description, and existing comments to understand the context. Use the issue's domain terminology in your draft.
Thread analysis — when comments exist on the issue, analyze the last 3-5 comments to understand the conversation dynamics:
Example with thread context: references/example-comment-with-context.md
If no issue key was provided, skip this step entirely.
The user's input may be rough, unstructured, or dictated by voice. Transform it into a clear, well-written comment:
Clean prose, 1-3 paragraphs. Direct reply or note — no headings, no greetings, no sign-offs.
[1-3 paragraphs. Concise, direct response addressing the issue or question.]
Example: references/example-comment.md
Structured list with a brief context line and prioritized bullet points.
[1-2 sentences of context — what was reviewed and in what scope.]
- [Feedback item — most critical first]
- [Feedback item]
- [Feedback item]
Rules:
-)Example: references/example-feedback-list.md
Structured code review findings condensed for a JIRA comment. Expects input from a triaged review — after the triage skill has classified findings into Fix Now / Fix Later / Skip groups. Transforms the triage output into an actionable, scannable summary that developers can work through as a checklist.
**Code Review: {branch-name}** | {date} | Verdict: {verdict}
{reviewer-list} | {finding-count} findings | ~{total-effort}
{AI Slop: X/10 — only if score <= 6}
### Fix Now ({group-count} groups, ~{effort})
**{Group Name}**
- [ ] `[BE-001]` **Issue title** — `file:line` — description + fix
- [ ] `[SC-002]` **Issue title** ↔️CROSS — `file:line` — description + fix
> {Why fix now — copied from triage reasoning}
**{Group Name}**
- [ ] `[VM-001]` **Issue title** — `file:line` — description + fix
### Fix Later ({count} findings)
- `[QA-001]` Issue title — `file:line`
- `[FE-001]` Issue title — `file:line`
{Skip: N findings omitted} | Full report: `{report-path}`
Rules:
>) so the developer knows why this is urgent.VM-, BE-, FE-, QA-, SC-, DV-) for traceability back to the full report↔️CROSS tags with reviewer attribution on cross-reviewer findingsExample: references/example-pr-review.md
Always present the draft inside a clearly marked block and ask:
JIRA Comment Draft — please review:
[comment content]
Confirm to send, or let me know what to change.
When thread context was used (comments existed on the issue), include a brief context note above the draft so the user knows what influenced the tone and framing:
Thread context: Last 3 comments discuss staging regression. Most recent (Anna, 2h ago) asks for confirmation on the date filter. Draft framed as a direct answer.
Do NOT send to JIRA until the user explicitly confirms.
After the user confirms the draft, resolve the JIRA connection before sending.
The skill needs a JIRA cloudId (e.g. mycompany.atlassian.net). The projectKey is not needed — the issue key already identifies the project.
Resolution order:
CLAUDE.md for a JIRA config block:
## JIRA
- Cloud: mycompany.atlassian.net
AskUserQuestion (header: "JIRA config") for the cloud ID.Store the resolved value for the rest of the session.
After configuration is resolved, use the addJiraComment MCP tool:
AskUserQuestion (header: "Issue key") if not provided earliernpx claudepluginhub mrstroz/claude-code-plugins --plugin jiraCreates Jira issues via CLI flags or work-item files. Converts Markdown body to ADF, previews payload, requires confirmation, then POSTs to Jira.
Fetches a JIRA issue and distills it into a structured task with acceptance criteria, sprint context, and codebase analysis. Surfaces missing criteria, scope, and risks, and can enrich the JIRA issue with analysis or spawn sub-tickets.
Collaborate on JIRA issues: add/edit/delete comments, upload/download attachments, manage watchers, send notifications, view activity via jira-as CLI.