ticket-tracker

Track software work as markdown tickets backed by SQLite rule enforcement.

Updated May 28, 2026
One-click install
npx skills add https://github.com/tgiachett/agent-c2 --skill ticket-tracker-tgiachett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-tracker
Source: https://github.com/tgiachett/agent-c2/tree/main/tickets/ticket-tracker-skill
Command: npx skills add https://github.com/tgiachett/agent-c2 --skill ticket-tracker-tgiachett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the overhead of tracking software work in separate systems by keeping tickets as human-readable markdown files backed by a local SQLite workflow engine.

Core Features & Use Cases

  • Markdown round-trip: Tickets stay in git as editable markdown while the CLI keeps state consistent in SQLite.
  • Workflow enforcement: Create, claim, transition, block, and close tickets with lifecycle and dependency checks.
  • Team coordination: Link commits, generate changelogs, register agent roles, detect code-surface conflicts, and review work in an optional GUI.
  • Use Case: A team can manage multi-agent repo work entirely inside the repository without a server, SaaS tool, or external database service.

Quick Start

Use the ticket tracker skill to set up repo tickets, manage their lifecycle, and keep commit-linked status updates in markdown.

Frequently Asked Questions about ticket-tracker

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

FAQPage Schema
How do I track software tickets inside a git repository using markdown?

You can track software tickets inside a git repository by storing them as human-readable markdown files while a local SQLite engine enforces workflow rules and state consistency. This approach keeps ticket data version-controlled alongside your source code without requiring external services.

Can I manage multi-agent repository workflows without a dedicated ticket server?

Multi-agent repository workflows can be managed entirely in-repo without a server or SaaS tool. The system supports an agent roster for role registration, dependency linking, conflict detection, and commit enrichment to coordinate work across multiple contributors.

How do I generate a changelog from markdown tickets linked to git commits?

Generating a changelog from markdown tickets linked to git commits is supported natively. The tracker enriches git commits with ticket status updates and compiles them into a changelog, ensuring your release notes reflect actual work completed within the repository.

Does in-repo ticket tracking work with Python and what are the setup requirements?

In-repo ticket tracking requires a Python 3.8+ environment using only the standard library. You need to install the provided CLI tool to manage ticket lifecycles, enforce dependency gating, and maintain markdown round-tripping with the local SQLite database.

What is the best way to prevent code-surface conflicts when multiple agents edit the same repository?

Preventing code-surface conflicts during multi-agent edits is handled by built-in conflict detection. The tracker monitors assigned ticket surfaces and alerts agents to overlapping modifications before they occur, reducing integration issues and maintaining workflow consistency.

Why use markdown files with SQLite for ticket tracking instead of a standalone database?

Using markdown files with SQLite backing combines human-readable, git-friendly ticket storage with strict workflow enforcement. Markdown round-tripping ensures tickets remain editable in git, while SQLite guarantees state consistency, dependency gating, and lifecycle validation.