メニュー
Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Query an independent peer or a configurable local/OpenRouter review panel, with distinct quorum and evidence-backed consensus interpretation policies.
Safely coordinate bounded delegation while preserving observable outcome and acceptance-evidence pairs through one-writer execution, independent review, and parent validation. Explicit invocation only.
Detect whether a beads repository needs classic-to-Dolt migration or an in-place Dolt schema upgrade.
Migrate beads from classic SQLite/JSONL to Dolt, or safely upgrade an existing Dolt schema after a bd upgrade.
Read-only current-session and UTC-week token telemetry dashboard for Pi, Claude Code, Codex, and optional OpenRouter management analytics.
Read-only audit of Pi routing and configured second-opinion panel model IDs against the active Pi catalog and public live model metadata; reports when Pi or configured models merit review without editing config.
| name | jira-ticket |
| description | Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements. |
| allowed-tools | mcp__jira__*,ToolSearch |
| model-tier | economy |
| model | haiku |
| effort | medium |
| version | 1.2.0 |
| author | flurdy |
Fetch details about a Jira ticket.
This skill requires the mcp-server-atlassian-jira MCP server configured with the name jira.
/jira-ticket SP-123
Use the Jira MCP tools to fetch the ticket details:
mcp__jira__jira_get with:
path: /rest/api/3/issue/{ticketNumber}
jq: "{key: key, summary: fields.summary, type: fields.issuetype.name, description: fields.description}"
If mcp__jira__jira_get is not yet loaded (common on the first prompt of a session — MCP tools are deferred until first referenced), don't bail out. Instead:
ToolSearch with query: "select:mcp__jira__jira_get" to load its schema.mcp__jira__jira_get call.ToolSearch returns no match — the jira MCP server is not configured for this project, not just lazy-loaded. Tell the user, and either:
~/.claude.json mcpServers.jira block if they want to copy it across (do not edit ~/.claude.json without explicit consent).Treat a missing MCP server as "ask the user," not as a hard failure.
Map the Jira issue type to a conventional commit prefix:
| Issue Type | Branch Prefix |
|---|---|
| Story | feat |
| Task | feat |
| Bug | fix |
| Spike | chore |
| Sub-task | inherit from parent, or feat |
| Improvement | feat |
| Technical Debt | refactor |
| Documentation | docs |
| Default | feat |
Provide the user with:
SP-123)Ticket: SP-123
Summary: Add user authentication
Type: Story
Suggested prefix: feat
Branch name: feat/SP-123-add-user-authentication