fetch-ticket

Name: fetch-ticket
Availability: InStock
Author: nicolas

Aggregate ticket information from YouTrack, GitHub, or local files into normalized markdown.

Updated Jan 15, 2026

Search Tags:#automation #github #fetch #normalization #ticket #ticketing #youtrack

Ready to run

npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill fetch-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fetch-ticket
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/fetch-ticket
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill fetch-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch-ticket aggregates ticket information from YouTrack, GitHub, or local files into a normalized markdown representation.

Core Features & Use Cases

Source-agnostic ticket retrieval: YouTrack, GitHub issues/PRs, or plain files, with automatic source detection.
Normalized output: Consistent title, description, status, priority, labels, assignees, and discussion extracted for downstream automation.
Use Case: When consolidating multiple tickets across systems for a release plan, fetch-ticket provides a single source of truth.

Quick Start

Provide a ticket ID in any supported format to fetch-ticket and receive a normalized markdown ticket document.

Frequently Asked Questions about fetch-ticket

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

FAQPage Schema

How do I normalize ticket data from YouTrack and GitHub into a single format?▼

To normalize ticket data, fetch-ticket aggregates title, description, status, priority, labels, assignees, and comments from YouTrack or GitHub into a consistent markdown representation for downstream automation.

Can fetch-ticket automatically detect whether a ticket is from YouTrack or GitHub?▼

Yes, fetch-ticket automatically detects the source from common ticket ID patterns, supporting YouTrack issues, GitHub issues and pull requests, or pre-saved local files without manual source specification.

How do I consolidate multiple tickets across different systems for a release plan?▼

You consolidate multiple tickets by providing ticket IDs in any supported format to fetch-ticket, which retrieves and normalizes each ticket into a single markdown document suitable for release planning.

What ticket fields are extracted when aggregating issues from GitHub and YouTrack?▼

Fetch-ticket extracts the ticket title, description, status, priority, labels, assignees, and comments, outputting all fields in a normalized markdown document regardless of the original source system.

Do I need to specify a source system when fetching a ticket ID?▼

No, you do not need to specify a source system manually because fetch-ticket detects the source automatically from common ticket ID patterns associated with YouTrack, GitHub, or local files.

Can I use local files as a ticket source for normalization alongside GitHub issues?▼

Yes, you can use pre-saved local files as a ticket source alongside GitHub issues and YouTrack tickets, and fetch-ticket normalizes the file contents into the same consistent markdown output format.