tk-issue-tracking

Manage ticket lifecycles and sync statuses with code commits using the tk tool.

1|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/mbtz/agent-skills --skill tk-issue-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tk-issue-tracking
Source: https://github.com/mbtz/agent-skills/tree/main/skills/tk-issue-tracking
Command: npx skills add https://github.com/mbtz/agent-skills --skill tk-issue-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines your workflow by integrating ticket management directly into your development process using the tk tool.

Core Features & Use Cases

  • Ticket Management: Use tk commands to manage the lifecycle of your tickets (ready, in progress, closed).
  • Code Sync: Ensures your tickets in .tickets/ are kept in sync with your code changes.
  • Use Case: When you start working on a bug, you can use tk start <bug-id> to mark it as in progress and then commit your code changes along with the updated ticket status.

Quick Start

List all ready tickets by running tk ready.

Frequently Asked Questions about tk-issue-tracking

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

FAQPage Schema
How do I track issue status alongside code commits in a local development workflow?

Issue tracking and ticket lifecycles are managed using the `tk` command-line tool, which synchronizes ticket status directly with code commits within a project's `.tickets/` directory to streamline your workflow.

What is the best way to manage ticket lifecycles without leaving the command line?

Managing ticket lifecycles is handled by the `tk` tool, which supports ticket creation, status updates like ready, start, and close, and organizes tickets by type, priority, and description in the `.tickets/` directory.

How do I mark a bug ticket as in progress before committing code changes?

To mark a bug ticket as in progress, run the `tk start <bug-id>` command, which updates the ticket status and ensures your tickets in `.tickets/` are kept in sync with your code changes.

How can I list all ready tickets in my current project?

To list all ready tickets in your current project, execute the `tk ready` command, which queries the `.tickets/` directory and displays tickets available for development.

Does this issue tracking approach require a separate database or external server?

This issue tracking approach does not require a separate database or external server, as it facilitates development workflows by storing and synchronizing ticket statuses locally within a project's `.tickets/` directory.

Can I organize tickets by type and priority using command line issue tracking?

Yes, you can organize tickets by type, priority, and description using the `tk` command-line tool, which manages the ticket lifecycle and stores these attributes within the project's local `.tickets/` directory.