jira-ticket
npx machina-cli add skill flurdy/agent-skills/jira-ticket --openclawJira Ticket Lookup
Fetch details about a Jira ticket.
Requirements
This skill requires the mcp-server-atlassian-jira MCP server configured with the name jira.
Usage
/jira-ticket SP-123
Instructions
1. Look Up the Jira Ticket
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}"
2. Determine Branch Prefix
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 |
3. Return Ticket Info
Provide the user with:
- Ticket key (e.g.,
SP-123) - Summary
- Issue type
- Suggested branch prefix based on type
- Description (if available and requested)
Example Output
Ticket: SP-123
Summary: Add user authentication
Type: Story
Suggested prefix: feat
Branch name: feat/SP-123-add-user-authentication
Source
git clone https://github.com/flurdy/agent-skills/blob/main/skills/jira-ticket/SKILL.mdView on GitHub Overview
jira-ticket retrieves key details from a Jira issue (key, summary, type, description) via the MCP server named jira. This context supports consistent branch naming, accurate PR descriptions, and quick understanding of ticket requirements.
How This Skill Works
It queries the Jira MCP server with mcp__jira__jira_get to fetch /rest/api/3/issue/{ticketNumber} and extracts key, summary, type, and description. It then maps the issue type to a conventional branch prefix (e.g., Story -> feat, Bug -> fix) and returns a structured summary including a suggested branch name.
When to Use It
- When naming a feature or bug fix branch from a Jira ticket.
- Before creating a PR to ensure the title and context reference the Jira issue.
- When skim-reading ticket details to confirm scope and requirements.
- When communicating changes to teammates, tying work back to the Jira ticket.
- When documenting changes that should be traceable to a Jira issue.
Quick Start
- Step 1: Look up the Jira ticket using mcp__jira__jira_get with path /rest/api/3/issue/{ticketNumber} and a jq filter to retrieve key, summary, type, and description.
- Step 2: Map the issue type to a branch prefix (e.g., Story -> feat, Bug -> fix) and prepare a branch name format.
- Step 3: Return the ticket info including Ticket key, Summary, Type, Suggested prefix, and a constructed Branch name.
Best Practices
- Always fetch key, summary, type, and description in a single request.
- Use the type-to-prefix mapping to keep conventional branch naming (e.g., Story -> feat, Bug -> fix).
- Include both the ticket key and a descriptive slug in the branch name (e.g., feat/SP-123-add-user-auth).
- Handle missing descriptions gracefully and provide a sensible fallback.
- Validate branch name against repository naming rules before creating a PR.
Example Use Cases
- Ticket: SP-123; Summary: Add user authentication; Type: Story; Suggested prefix: feat; Branch name: feat/SP-123-add-user-authentication
- Ticket: PROJ-456; Summary: Fix login crash; Type: Bug; Suggested prefix: fix; Branch name: fix/PROJ-456-fix-login-crash
- Ticket: MY-789; Summary: Load testing spike; Type: Spike; Suggested prefix: chore; Branch name: chore/MY-789-load-testing-spike
- Ticket: DOC-101; Summary: Update API docs; Type: Documentation; Suggested prefix: docs; Branch name: docs/DOC-101-update-api-docs
- Ticket: TKT-555; Summary: Refactor legacy module; Type: Improvement; Suggested prefix: feat; Branch name: feat/TKT-555-refactor-legacy-module
