jira-report-comment

# Jira Report Comment Generate a short Jira comment describing what shipped on a ticket, and save it as a local markdown file. The reader — a PM, QA engineer, or architect — already has the ticket open. Every sentence that paraphrases the ticket back at them is a sentence they skip, and after two of those they stop reading the whole comment. So the comment carries only what the ticket cannot: what actually shipped, and what someone downstream now has to do differently. By default that is one summary paragraph. Bug fixes add a Root Cause. Verify and Deploy sections appear only when the diff gives a concrete reason. ## Step 1 — Resolve the issue key In order: the key the user gave you; otherwise the first `[A-Z]+-[0-9]+` match in `git branch --show-current`; otherwise ask. Confirm before continuing: "I detected **CX-4328** from your branch. Use this issue key?" Then reserve the output file, and write to this same path for the rest of the session — re-running the skill for the same issue updates the file rather than adding another: ```bash mkdir -p docs/jira-reports touch "docs/jira-reports/$(date +%Y-%m-%d-%H%M%S)-<ISSUE_KEY>.md" ``` ## Step 2 — Fetch the ticket Try `mcp__atlassian__getJiraIssue` with the key. If it is unavailable, ask the user to paste the title, description, and acceptance criteria. Read the title, description, type, and status. **This is the material to leave out, not material to write from.** Use it as the exclusion list. ## Step 3 — Gather the ...