ticket-tracker

Automate ticket lifecycle management with smart defaults and PR-based status updates.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/cbown75/ai --skill ticket-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-tracker
Source: https://github.com/cbown75/ai/tree/main/.claude/skills/ticket-tracker
Command: npx skills add https://github.com/cbown75/ai --skill ticket-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ticket-tracker automates the end-to-end ticket lifecycle for development projects, enabling create/epic linkage, status automation, and guided prompts to fill missing info.

Core Features & Use Cases

  • Smart defaulting: creates tickets with consistent defaults to accelerate intake.
  • Epic discovery and linkage: automatically associates tickets with active epics or asks for user input when ambiguous.
  • Status automation: updates tickets in response to PR events and branch activities to keep state in sync with development.
  • Workflow integration: works with dev-workflow and git-conventions skills to maintain traceability and consistency.

Quick Start

Ask Claude to create a new ticket by providing a brief summary; the skill will fill in details, set defaults, and link to epics as discovered.

Frequently Asked Questions about ticket-tracker

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

FAQPage Schema
How do I automate Jira ticket creation with smart defaults for development projects?

Automate Jira ticket creation by providing a brief summary; the system fills in missing details, applies consistent defaults, and links the ticket to active epics automatically to accelerate intake.

Can I auto-update ticket status when a pull request is created?

Yes, auto-update ticket status by tracking PR events and branch activities, keeping the ticket state in sync with development progress without manual intervention.

How does epic discovery and linkage work when creating tickets?

Epic discovery automatically associates new tickets with active epics, prompting for user input via AskUserQuestion only when the linkage is ambiguous.

Does ticket-tracker work with Linear as well as Jira for CLI integration?

Yes, CLI integration supports both Jira and Linear, enabling ticket creation, epic linkage, and status transitions directly from the command line for either platform.

What's the best way to manage ticket state transitions across the development lifecycle?

Manage ticket state transitions by integrating with dev-workflow and git-conventions skills, maintaining traceability and consistency through automated PR and branch event tracking.

Do I need to provide all ticket details upfront, or will the system prompt for missing information?

You do not need to provide all details upfront; the system applies smart defaults for missing fields and uses AskUserQuestion prompts to gather required information only when necessary.