/update-jira

Update Jira Task

> **Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.

Update a Jira task with a summary of the fix implementation.

Usage

/update-jira <task_id>

**Arguments:**

• `task_id` - The Jira task ID (e.g., PROD-4070, <JIRA_KEY>-XXXX)

**Examples:**

/update-jira PROD-4070
/update-jira <JIRA_KEY>-XXXX

Instructions

When this skill is invoked:

1. **Parse the task ID** from `$ARGUMENTS`

2. **Gather context from the current session**:

• Check git log for recent commits on current branch
• Check for any open PRs from current branch using `gh pr view`
• Identify changed files from commits

3. **Build the update comment** with:

• **PR link** (if available)
• **Problem summary** - What was the issue
• **Solution summary** - How it was fixed
• **Files changed** - List of modified files
• **Result** - What the fix accomplishes

4. **Post comment to Jira**:

• Use `mcp__claude_ai_Atlassian__addCommentToJiraIssue`
• cloudId: `<jira-host>`
• issueIdOrKey: the task ID
• contentFormat: `markdown`

5. **Confirm success** with link to Jira task

Comment Template

## Fix Implemented

**PR:** <pr_url>

### Problem
<brief description of the issue>

### Solution
<what was changed and why>

### Files Changed
- <file1>
- <file2>

### Result
<what the fix accomplishes>

Notes

• Extracts information from git history and PR details automatically
• Uses the current branch context to determine what was done
• Keep descriptions concise but informative