fixme-tickets

Route ticket and session operations to the backend configured in .fixme/config.json.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/denis-pingin/fixme --skill fixme-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixme-tickets
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-tickets
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tickets and session management across multiple backend implementations are unified, enabling a single interface to route operations to the configured backend.

Core Features & Use Cases

  • Abstract ticket interface that routes ticket and session operations to the chosen backend (fixme-tickets-md, fixme-tickets-linear, etc).
  • Dynamic backend resolution from .fixme/config.json and dispatches to the corresponding backend skill.
  • Use case: You can switch between backends without changing your integration code, by updating config.json.

Quick Start

Use fixme-tickets to create and manage tickets using the backend defined in .fixme/config.json.

Frequently Asked Questions about fixme-tickets

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

FAQPage Schema
How do I route ticketing operations to a specific backend?

Route ticketing operations by defining the target backend in your project's .fixme/config.json file. The skill dynamically resolves this configuration and dispatches create, transition, list, and summary operations to the corresponding backend skill.

How do I switch between markdown and linear backends for session management?

Switch between markdown and linear backends by updating the active backend value in .fixme/config.json. This allows you to change ticketing systems without modifying your underlying integration code or altering the uniform API surface.

What is a unified ticket interface for multiple backends?

A unified ticket interface abstracts session management by exposing a single API for create, transition, list, next, rename, and summary operations. It uses context-aware dispatch to route commands to whatever backend is configured.

Can I manage tickets across different platforms without changing integration code?

Yes, you can manage tickets across different platforms without changing code. The skill reads the active backend from .fixme/config.json and dynamically dispatches operations, ensuring your integration code remains unchanged during backend switches.

Do I need a config.json file to manage ticket sessions?

Yes, a .fixme/config.json file is required to manage ticket sessions. The skill depends on this configuration file to dynamically resolve the active backend and dispatch ticketing operations to the correct skill.

Why does my ticket routing not switch to the new backend?

Ticket routing fails to switch if the .fixme/config.json file is missing, improperly formatted, or points to an unsupported backend. Ensure the configuration is valid so the dynamic backend resolution can successfully dispatch operations.