ticket-provider

Read CLAUDE.md to route ticket operations to GitHub Issues or an external API.

1|1|Updated Mar 5, 2026

Search Tags:#routing #github #claude.md #ticket #provider #issues-api

Ready to run

npx skills add https://github.com/dokipen/claude-cadence --skill ticket-provider

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-provider
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/ticket-provider
Command: npx skills add https://github.com/dokipen/claude-cadence --skill ticket-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ticket provider abstraction layer that reads CLAUDE.md configuration and dispatches to the correct backend (GitHub Issues or issues API). Use when performing ticket operations across multiple backends.

Core Features & Use Cases

Reads the consuming project's CLAUDE.md to determine which ticket provider to use (GitHub Issues by default or an external API).
Dispatches common ticket operations (list, view, create, update, label, comment, close) to the selected backend.
Enables project teams to unify ticket workflows without changing client code or command syntax.

Quick Start

Configure CLAUDE.md with a Ticket Provider section to enable automatic routing of ticket operations.

Frequently Asked Questions about ticket-provider

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

FAQPage Schema

How do I route ticket operations across multiple backends in a CLAUDE Code project?▼

Ticket routing across backends is handled by reading CLAUDE.md configuration and dispatching operations. It defaults to GitHub Issues but can route to an external issues API, unifying ticket workflows without changing client command syntax.

How do I configure ticket provider detection using CLAUDE.md?▼

Ticket provider detection is configured by adding a Ticket Provider section to your project's CLAUDE.md. This setup enables automatic routing of list, view, create, update, label, comment, and close operations to the correct backend.

What is the default backend when no specific ticket provider is configured?▼

GitHub Issues is the default backend for ticket operations when no specific provider is configured. The system automatically delegates operations to GitHub unless CLAUDE.md specifies an external issues API.

Can I use the same ticket commands for an external issues API and GitHub Issues?▼

Ticket commands remain unified across GitHub Issues and external issues API backends. This abstraction layer delegates operations seamlessly, allowing project teams to execute ticket workflows without altering client code or command syntax.

Do I need external dependencies to automate ticket routing for CLAUDE Code?▼

No external dependencies are required to automate ticket routing for CLAUDE Code projects. The provider operates independently using internal scripts to parse CLAUDE.md and dispatch ticket operations to the selected backend.