How do I install the Jira Sync skill?

Run npx skillmds@latest add majiayu000/jira-sync-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jira Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jira Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jira Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jira Sync?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jira Sync by majiayu000 — Agent Skill

Name: Jira Sync
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

JIRA Ticket Sync

Sync current plan progress to JIRA ticket: $ARGUMENTS

If no argument provided, search for a ticket URL in the active plan file (most recently modified .md in plans/).

Workflow

Step 1: Identify Ticket and Context

Parse ticket ID from $ARGUMENTS or extract from the active plan file
Fetch current ticket state via JIRA MCP (mcp__atlassian__getJiraIssue)
Determine current milestone by checking:
- Does a plan file exist? → Plan created
- Is there a working branch? → Implementation started
- Are tasks in progress? → Active implementation
- Is there an open PR? → PR ready for review
- Is the PR merged? → Complete

Step 2: Gather Update Content

Based on the current milestone:

Milestone	Content to Post
Plan created	Plan summary, branch name, link to PR (if draft exists)
Implementation in progress	Task completion summary (X of Y tasks done), any blockers
PR ready	PR link, summary of changes, test results
PR merged	Final summary, suggest moving ticket to "Done"

Step 3: Post Update

Add a comment to the ticket with the gathered content via JIRA MCP
Update ticket fields if applicable:
- Add branch name to a custom field or comment
- Add PR link to a custom field or comment
Report what was synced to the user

Step 4: Suggest Status Transition

Based on the milestone, suggest (but don't automatically perform) a status transition:

Milestone	Suggested Status
Plan created	"In Progress"
PR ready	"In Review"
PR merged	"Done"

Important Notes

Never auto-transition ticket status — always suggest and let the user confirm
Idempotent updates — running sync multiple times at the same milestone should not create duplicate comments
Comment format — use JIRA markdown with clear headers and bullet points

Execution

Sync the ticket now.

---name: jira-sync-2description: Syncs plan progress to a linked JIRA ticket. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep tickets in sync.--- # JIRA Ticket Sync Sync current plan progress to JIRA ticket: $ARGUMENTS If no argument provided, search for a ticket URL in the active plan file (most recently modified `.md` in `plans/`). ## Workflow ### Step 1: Identify Ticket and Context 1. **Parse ticket ID** from `$ARGUMENTS` or extract from the active plan file 2. **Fetch current ticket state** via JIRA MCP (`mcp__atlassian__getJiraIssue`) 3. **Determine current milestone** by checking: - Does a plan file exist? → Plan created - Is there a working branch? → Implementation started - Are tasks in progress? → Active implementation - Is there an open PR? → PR ready for review - Is the PR merged? → Complete ### Step 2: Gather Update Content Based on the current milestone: | Milestone | Content to Post | |-----------|-----------------| | **Plan created** | Plan summary, branch name, link to PR (if draft exists) | | **Implementation in progress** | Task completion summary (X of Y tasks done), any blockers | | **PR ready** | PR link, summary of changes, test results | | **PR merged** | Final summary, suggest moving ticket to "Done" | ### Step 3: Post Update 1. **Add a comment** to the ticket with the gathered content via JIRA MCP 2. **Update ticket fields** if applicable: - Add branch name to a custom field or comment - Add PR link to a custom field or comment 3. **Report** what was synced to the user ### Step 4: Suggest Status Transition Based on the milestone, suggest (but don't automatically perform) a status transition: | Milestone | Suggested Status | |-----------|-----------------| | Plan created | "In Progress" | | PR ready | "In Review" | | PR merged | "Done" | ## Important Notes - **Never auto-transition ticket status** — always suggest and let the user confirm - **Idempotent updates** — running sync multiple times at the same milestone should not create duplicate comments - **Comment format** — use JIRA markdown with clear headers and bullet points ## Execution Sync the ticket now.

Frequently asked questions

Jira Sync