Dev10x-ticket-create

Create GitHub, Linear, or JIRA tickets with structured titles, descriptions, and labels.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ticket-create-brave-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x-ticket-create
Source: https://github.com/Brave-Labs/dev10x/tree/main/codex-skills/dev10x-ticket-create
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ticket-create-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines ticket creation by formatting ticket content for GitHub, Linear, or JIRA, ensuring consistency and faster triage.

Core Features & Use Cases

  • Structured ticket data: builds titles, descriptions, and labels from context.
  • Multi-tracker support: targets GitHub, Linear, or JIRA with a single command.
  • Tailored templates: enforces Root Cause, Solution, and Files Changed sections.

Quick Start

Create a ticket from a recent code change by providing context and optional labels.

Frequently Asked Questions about Dev10x-ticket-create

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

FAQPage Schema
How do I create structured tickets for GitHub, Linear, or JIRA from code changes?

Create structured tickets by providing context to the automation workflow, which formats the data into a well-formed title, description, and labels for GitHub, Linear, or JIRA. It applies a consistent template including Root Cause, Solution, and Files Changed sections.

What is the best way to format a JIRA or Linear ticket with a Root Cause and Solution template?

The best way to format a JIRA or Linear ticket is using a tailored template that enforces Root Cause, Solution, and Files Changed sections. This ensures consistency across the tracker and speeds up triage.

Can I use a single command to create tickets across different trackers like GitHub Issues and JIRA?

Yes, you can target GitHub Issues, Linear, or JIRA with a single command. The workflow detects explicit tracker input or derives the target from repository defaults to route the ticket correctly.

How do I add labels to a GitHub Issue when generating it from provided context?

You can add labels to a GitHub Issue by providing optional labels alongside your context when generating the ticket. The workflow builds the complete ticket data including the labels automatically.

Does the ticket creation workflow derive the tracker from repository defaults automatically?

Yes, the workflow derives the tracker from repository defaults automatically when no explicit tracker input is detected. This streamlines the ticket creation process without requiring manual configuration.

Why should I use a structured template for creating Linear or JIRA tickets?

Using a structured template for Linear or JIRA tickets ensures consistency across your development team and enables faster triage. It standardizes Root Cause, Solution, and Files Changed sections for every issue.