菜单
Atlassian Jira integration via MCP. Use when working with Jira issues, tickets, epics, sprints, or project management. Supports searching, creating, updating issues, transitions, comments, and linking. Triggers when the user mentions Jira, tickets, issues, or project tracking.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
Review design specs for correctness, completeness, consistency, quality, implementability, and risks. Verifies claims against source code. Invoke with /review-spec <path-to-spec>.
Graphite CLI (gt) patterns for managing stacked pull requests. Use whenever the user mentions graphite, the `gt` command, PR stacks, or stacked diffs. Also triggers when starting development work in a repository where graphite is initialized (`.git/refs/graphite` exists or `gt` commands have been used). Invoke proactively when the user is creating branches, submitting PRs, or navigating between related branches in a collaborative repo — even if they don't mention graphite by name.
Use when creating issues, reviewing unestimated backlog items, or asked to estimate effort. Encodes the fibonacci scale and drives session/agent planning decisions.
Complete a development ticket end-to-end: root-cause any test failures, run the full test suite, lint and typecheck, commit, fast-forward merge to main, update the issue tracker to Done, and file follow-up issues for gaps. Invoke with /finish-ticket <ISSUE-ID>.
Session start check for MCP auth, git state, and worktree environment. Run at the start of any session involving MCP servers to surface expired tokens and env drift before they interrupt real work.
| name | jira |
| description | Atlassian Jira integration via MCP. Use when working with Jira issues, tickets, epics, sprints, or project management. Supports searching, creating, updating issues, transitions, comments, and linking. Triggers when the user mentions Jira, tickets, issues, or project tracking. |
| context | fork |
Use Atlassian MCP tools for Jira operations. This skill runs in a forked context to preserve the main conversation.
When returning results to the main conversation, provide:
| Operation | Tool | Use Case |
|---|---|---|
| Search | mcp__atlassian__searchJiraIssuesUsingJql | Find issues by JQL query |
| Get Issue | mcp__atlassian__getJiraIssue | Retrieve full issue details |
| Create | mcp__atlassian__createJiraIssue | Create new issues |
| Update | mcp__atlassian__editJiraIssue | Modify existing issues |
| Transitions | mcp__atlassian__getTransitionsForJiraIssue | Get available status changes |
| Transition | mcp__atlassian__transitionJiraIssue | Change issue status |
| Comment | mcp__atlassian__addCommentToJiraIssue | Add comments to issues |
| User Lookup | mcp__atlassian__lookupJiraAccountId | Find user account IDs |
| Projects | mcp__atlassian__getVisibleJiraProjects | List available projects |
| Issue Types | mcp__atlassian__getJiraProjectIssueTypesMetadata | Get project issue types |
# Issues assigned to current user
assignee = currentUser() AND status != Done
# Open issues in a project
project = "PROJ" AND status NOT IN (Done, Closed)
# Recently updated by me
updatedBy = currentUser() AND updated >= -7d
# Epics in a project
project = "PROJ" AND issuetype = Epic
# Issues with specific label
labels = "infrastructure" AND status = "In Progress"
# Dependencies (blocks/is blocked by)
issue in linkedIssues("PROJ-123", "blocks")
The MCP does not currently support creating issue links directly. Use the bundled script:
~/.claude/skills/jira/jira-link-issues PROJ-123 PROJ-456 "Depends On"
Common link types:
Depends On / Dependency of - Use for dependencies between issuesBlocks / Is Blocked By - Use for blocking relationshipsRelates To - General relationshipClones / Is Cloned By - For cloned issuesmcp__atlassian__getVisibleJiraProjects for available projectsmcp__atlassian__lookupJiraAccountId before assigningmcp__atlassian__searchJiraIssuesUsingJqlmcp__atlassian__getJiraIssuemcp__atlassian__getJiraProjectIssueTypesMetadatamcp__atlassian__lookupJiraAccountIdmcp__atlassian__createJiraIssuemcp__atlassian__getTransitionsForJiraIssuemcp__atlassian__transitionJiraIssue~/.claude/skills/jira/jira-link-issues SOURCE TARGET "Link Type"If MCP tools return errors, inform the user with specific guidance:
| Error | User Message |
|---|---|
| 401/403 Unauthorized | "Jira authentication failed. Please run /mcp to reconnect the Atlassian service." |
| 404 Not Found | "Issue or project not found. Please verify the key is correct." |
| 400 Bad Request | "Invalid field values. Check required fields for this issue type." |
| MCP unavailable | "Atlassian MCP is not connected. Please run /mcp to connect." |
Always surface authentication issues clearly so the user can resolve them.
See reference.md for complete JQL syntax and MCP tool documentation.