Parse Jira tickets to extract requirements and generate developer summaries.
npx skills add https://github.com/CoorpAcademy/claude-workshop --skill jira-ticket
Please help me install this Agent Skill. Skill: jira-ticket Source: https://github.com/CoorpAcademy/claude-workshop/tree/main/.claude/skills/jira-ticket Command: npx skills add https://github.com/CoorpAcademy/claude-workshop --skill jira-ticket
This Skill reads Jira tickets, extracts the problem statement and requirements, and presents a developer-friendly summary. It can optionally search the codebase for related files and, if requested, update ticket status with valid transitions to keep work aligned with the workflow.
To begin, run a simple query: /skill jira-ticket PROJ-456 Example: /skill jira-ticket PROJ-456 --search-codebase --status "In Progress"
High-intent search queries and answers about installing and using this skill.
Extract requirements from Jira tickets by parsing the ticket fields—summary, description, acceptance criteria, and comments—to identify problem statements and technical specifications. This Skill reads those fields directly via the Jira API and generates a developer-friendly summary highlighting what needs to be built.
Yes, this Skill can optionally search your codebase for files connected to a Jira ticket. After extracting requirements, it identifies relevant code files and dependencies, helping developers understand the scope and locate existing implementations or related modules.
Update ticket status by specifying a valid transition—such as 'In Progress' or 'Done'—within the Skill. It validates the transition against your Jira workflow rules before applying it, keeping ticket status synchronized with actual development progress.
This Skill extracts ticket summary, description, acceptance criteria, current status, assignee, priority, labels, and comments. It parses these fields to identify problem statements, technical requirements, and dependencies, then synthesizes them into an actionable developer brief.
Yes, you must provide a Jira API token and your Jira site URL for authentication. The Skill uses the Atlassian MCP integration to connect securely to your Jira instance and retrieve or update ticket data with proper credentials.
Jira ticket IDs must follow the PROJ-123 format, where PROJ is your project key and 123 is the ticket number. This format ensures the Skill correctly identifies and retrieves the right ticket from your Jira instance.
pramudityadManage Jira tickets via command line using REST API v3.
dudedesi12Track version histories, detect changes, and schedule content updates.
CodySwannGTSynchronize plan progress and development milestones to linked JIRA tickets.
elijahmurrayConfigure GitHub Issues, Linear, Jira, or GitLab for issue tracking.
