---
name: jira-link-work
description: Link git branches, commits, or pull requests to a Jira issue by posting a comment built FROM git data (traceability between code and ticket). Use only when the content comes from git — for free-text prose comments use jira-comment.
license: MIT
compatibility: Requires Atlassian Cloud Jira through Atlassian Rovo MCP v2 (https://mcp.atlassian.com/v2/mcp) with client-managed OAuth, plus a local Git repository.
---

# Jira Link Work

Link development artifacts (commits, branches, PRs) to Jira issues by posting a
structured comment **built from git data**, creating traceability between code and
tickets. The defining trait of this skill: the comment content is derived from git
(branch name, commit hashes, diff stats, PR URL), not dictated as prose.

## When to use

- User says "link my commit to PROJ-123"
- User says "link this PR to PROJ-789"
- User says "link my branch to PROJ-123"
- User says "link my Git work to PROJ-123"
- User provides a commit hash or PR URL to attach to an issue

## When NOT to use

- **Posting a free-text note or dictated prose** → use `jira-comment`
  (this skill only posts comments derived from git artifacts).
- **Completing the ticket** (comment + transition to done) → use `jira-complete`.
- **Creating the branch itself** → use `jira-branch`.

## Atlassian MCP conventions

1. Call `getAccessibleAtlassianResources` first and obtain the `cloudId` for the user's Jira Cloud site. If more than one site is returned, ask which to use; do not guess.
2. Pass that `cloudId` on every subsequent Jira tool call.
3. Call `addOrEditJiraIssueComment` to **add** a new comment. Omit any existing comment ID unless the user explicitly asked to edit a specific comment.

## How to respond

### Link current branch + recent commits

When the user says "link my Git work to PROJ-123":

1. Get the current branch name from git.
2. Determine the appropriate base branch from repository context or the user's request.
   If it cannot be determined safely, ask the user which base branch to use;
   never assume `main` or `development`.
3. Get recent commits on this branch compared with the confirmed base branch.
4. Format and post a structured comment to the issue.

**Comment format:**

```
🔗 Development Progress

Branch: feat/PROJ-123-fix-login-css
Base: <confirmed-base>

Commits:
• abc1234 — Fix responsive breakpoint for mobile nav
• def5678 — Add unit tests for nav component
• ghi9012 — Update snapshot tests

Files changed: 5 files (+120, -45)
```

### Link a specific commit

When the user says "link commit abc1234 to PROJ-123":

1. Get the commit details (hash, message, author, date, files).
2. Post a comment:

```
🔗 Commit Linked

abc1234 — Fix responsive breakpoint for mobile nav
Author: Shrey Purohit
Date: 2026-08-27 14:30 IST
Files: src/components/Nav.js, src/styles/nav.css
```

### Link a PR

When the user says "link PR #42 to PROJ-123" or provides a PR URL:

1. Extract the PR number/URL from the user's message.
2. Post a comment:

```
🔗 Pull Request

PR #42: Fix responsive breakpoint for mobile nav
URL: https://github.com/org/repo/pull/42
Status: Open
Branch: feat/PROJ-123-fix-login-css → <confirmed-base>
```

### Record Git progress update

When the user says "link my development progress to PROJ-123" or "record my
Git activity on PROJ-123":

1. Gather only the Git information relevant to the requested progress link.
2. Ask the user for a brief status note (optional).
3. Post a structured comment containing only information actually gathered:

```
📋 Progress Update

Branch: feat/PROJ-123-fix-login-css
Status: Implementation complete, tests passing
Commits: 5 since branch creation
Files changed: 8 files (+340, -120)

Notes: Login CSS fixed across mobile/tablet/desktop. All responsive breakpoints tested. Ready for review.
```

## Steps

### Step 1: Identify the issue key

Extract the Jira issue key from the user's request. If not explicitly mentioned, try to infer from the current branch name (e.g., `feat/PROJ-123-slug` → `PROJ-123`).

### Step 2: Gather git information

Use git commands to collect relevant data:

- `git branch --show-current` — current branch
- `git log --oneline <confirmed-base>..HEAD` — commits on this branch, when a safe base is known
- `git diff --stat <confirmed-base>..HEAD` — files changed summary, when relevant and a safe base is known
- `git show --stat <hash>` — specific commit details

If repository context does not identify a safe base branch, ask the user before
running comparisons. Do not substitute `main` or `development` by default.

### Step 3: Format the comment

Build the comment using the format appropriate to the linked artifact. Include
only the relevant information actually gathered, such as branch details for a
branch link, commit details for a commit link, PR details for a PR link, and
file summaries only when they are relevant and available.

### Step 4: Confirm and post

Show the comment preview to the user and ask for confirmation before posting via
`addOrEditJiraIssueComment` with `cloudId` and no comment ID (add, do not edit).

## Rules

- **Always confirm before posting** — show the exact comment that will be posted.
- **Add, do not silently edit.** Omit comment ID unless the user asked to edit a specific comment.
- **Never guess commit data** — only use what git returns.
- **Infer issue key from branch** when not explicitly provided (pattern: `feat/<KEY>-slug`).
- **Keep comments concise** — max 10 commits listed; if more, summarize with "... and N more commits".
- **Use the issue key** the user provides, not one from a different ticket.
- **Report only artifact-specific information**: commit details for commit links, PR details for PR links, branch details for branch links, and file summaries only when actually gathered and relevant.
- **Never include file contents or full diffs** in comments — only relevant metadata such as paths and line counts.
- **Respect privacy** — don't include author emails, only names.

## Error handling

- **Not a git repository**: Report "Not in a git repository" and stop.
- **No commits on branch**: Report "No commits found on this branch relative to base."
- **Issue not found**: Report the Jira error clearly.
- **Branch doesn't match any issue**: Ask the user which issue to link to.
- **Comment post fails**: Report the error and show the comment so the user can post manually.