Menu
Interact with Jira and Confluence. Use the Atlassian MCP server tools when available, otherwise fall back to the jira CLI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Goal-driven execution. Breaks a task into phases with verification, parallelizes via subagents, and iterates until the outcome is achieved. Triggers: 'go-do', 'goal-driven', 'achieve this', 'make it so'.
Do work in an isolated git worktree instead of switching branches. Use when creating a branch and opening a PR so the user's working directory is never disturbed. Triggers: 'create a branch', 'open a PR', 'make a change on a new branch'.
Record a demo of a web application or terminal session. Uses Playwright for browser recordings and VHS for terminal recordings. Offers to attach the resulting GIF/video as a PR comment.
Start an interactive questionnaire when there are more than 5 options or bullet points that need to be addressed. Uses the ask_user tool to walk through selections interactively instead of dumping a wall of text.
Code review mode. Read and analyze code, PRs, and issues. All GitHub write operations are prohibited.
Take a screenshot of a running web application using Playwright and Chromium. Offers to attach the screenshot as a PR comment.
| name | atlassian |
| description | Interact with Jira and Confluence. Use the Atlassian MCP server tools when available, otherwise fall back to the jira CLI. |
| user-invocable | false |
Any reference matching the pattern [A-Za-z]{2,4}-\d+ (2–4 letters, a dash,
then one or more digits — e.g. CP-78, cp-78, ENG-1234, abcd-5) is a Jira
issue key. When the user mentions one of these:
cp-78 → CP-78).jira_get_issue / jira_update_issue tools (or CLI fallback)
to interact with it.gh issue comment.GitHub issues are referenced with a bare #78 (hash prefix, no letters).
A letter-prefix like CP-78 or cp-78 is never a GitHub issue.
When given an Atlassian URL, extract identifiers directly:
https://fastly.atlassian.net/wiki/spaces/.../pages/<PAGE_ID>/... → use page ID with confluence_get_pagehttps://fastly.atlassian.net/browse/PROJ-123 → use key with jira_get_issueconfluence_get_page — fetch a page by IDconfluence_search — CQL queries (e.g. title = "Varnishlog")jira_get_issue — fetch by key (e.g. PROJ-123)jira_search — JQL queries (e.g. summary ~ "X" AND issuetype = Epic)jira_create_issue, jira_update_issue — create/edit issuesjira_get_transitions, jira_transition_issue — workflow transitionsUse the jira CLI (jira-cli-go):
jira issue list -q "summary ~ 'control cache' AND issuetype = Epic"
jira issue view PROJ-123
jira epic list --project PROJ
jira issue create -t Bug -s "Title" -b "Description" -P PROJ
jira issue move PROJ-123 "In Progress"