skills.rest
duronext
duronextOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ticket

Create and route tickets across Linear, GitHub Issues, or Jira using jig.config.md.

15|1|Updated Mar 29, 2026
Search Tags:#automation#workflow#consistency#ticket#tracking#project-management#ticketing
One-click install
npx skills add https://github.com/duronext/jig --skill ticket-duronext
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/duronext/jig/tree/main/core/skills/ticket
Command: npx skills add https://github.com/duronext/jig --skill ticket-duronext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create tickets consistently across different trackers by interpreting natural prompts and routing to the correct tracker pack, reducing miscommunication and manual work.

Core Features & Use Cases

  • Unified ticket creation: Generate and file tickets in Linear, GitHub Issues, or Jira based on jig.config.md.
  • Context-aware drafting: Proposes clear titles and descriptions aligned with your team's workflow.
  • Kickoff-ready workflows: Works with /jig:ticket or prompts like 'create a ticket' to start the process.

Quick Start

Tell Jig to create a ticket by saying 'create a ticket to fix login issue' or use /jig:ticket to start the workflow.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I automate ticket creation across multiple project trackers like Linear, Jira, and GitHub Issues?▼

Automated ticket creation across multiple trackers is handled by reading jig.config.md to route natural language prompts to the correct tracker pack. This ensures consistent intake for issues, features, and tasks across Linear, GitHub Issues, or Jira without manual formatting.

What is needed to configure ticket routing for consistent project management intake?▼

Configuring ticket routing requires a jig.config.md file specifying ticket-system, ticket-prefix, and branching rules. This setup directs the workflow to invoke the correct tracker pack and enforce consistency across your project's ticketing system.

How do I create a ticket using a natural language prompt in my workflow?▼

To create a ticket, trigger the workflow by saying 'create a ticket to fix login issue' or using the /jig:ticket command. The system interprets your natural prompt and drafts a context-aware title and description aligned with your team's workflow.

Does automated ticket drafting work with existing branching rules and ticket prefixes?▼

Automated ticket drafting works directly with existing branching rules and ticket prefixes defined in your jig.config.md file. It uses these configurations to route prompts accurately and generate kickoff-ready tickets for your specific tracker environment.

Why does my ticket creation workflow return inconsistent results across different trackers?▼

Inconsistent ticket creation results occur when jig.config.md lacks proper ticket-system, ticket-prefix, or branching rules definitions. Correct configuration ensures the workflow invokes the correct tracker pack to generate clear, consistent tickets across Linear, GitHub Issues, or Jira.

Related Skills

Explore More Product & Management Skills→
duronextduronext
15

pr-create

Create pull requests with descriptions and test plans from branch commits using gh.

Official
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:ticket-create

Create structured issue tracker tickets with predefined formatting and label inference.

Official
Intermediate
ma08ma08
28

start-task

Create standardized task folders with tracker-aware names and session metadata.

Community
Advanced
JmarquesJmarques

wayfinder

Create a shared issue map on an issue tracker for incremental project resolution.

Community
Advanced