Work on Ticket

Fetch Jira or Linear ticket details, create a Git branch, and generate a task breakdown.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Zeyden/claude-skills --skill work-on-ticket-zeyden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Work on Ticket
Source: https://github.com/Zeyden/claude-skills/tree/main/skills/work-on-ticket
Command: npx skills add https://github.com/Zeyden/claude-skills --skill work-on-ticket-zeyden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the initial setup for working on a new ticket, streamlining the process of creating branches and planning tasks.

Core Features & Use Cases

  • Ticket Integration: Fetches details from Jira or Linear tickets.
  • Automated Branching: Creates Git branches with names derived from ticket IDs and summaries.
  • Task Planning: Generates a structured task breakdown for implementation.
  • Use Case: When you're assigned a new bug or feature, use this Skill to instantly create a correctly named branch and get a clear plan for tackling the work.

Quick Start

Use the work on ticket skill to start working on ticket PROJ-123.

Frequently Asked Questions about Work on Ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating a Git branch from a Jira or Linear ticket?

This Skill fetches Jira or Linear ticket details and automatically creates a Git branch named using the ticket ID and summary, ensuring a clean Git state before branching.

Can I generate a task breakdown plan when starting work on a new ticket?

Yes, you can generate a structured task breakdown plan when starting work on a new ticket. This Skill initiates a task planning workflow alongside branch creation to provide a clear implementation plan.

Does the branching workflow check for a clean Git state before creating a new branch?

Yes, the branching workflow ensures a clean Git state before creating a new branch. This prevents unresolved changes from interfering with the automated branch creation process.

What is the best way to start coding tasks efficiently from issue trackers?

The best way to start coding tasks efficiently is to use an automated workflow. This Skill fetches Jira or Linear details, creates a Git branch, and generates a structured task breakdown in one step.

How do branch names get generated when fetching details from Jira or Linear?

Branch names are generated by combining the ticket ID and summary fetched directly from Jira or Linear. This ensures your Git branches are consistently and correctly named based on issue tracker data.