issue-tracking

Manage Markdown-based issue tickets and dependencies via a portable CLI.

Updated Mar 9, 2023
One-click install
npx skills add https://github.com/rogvid/dotfiles --skill issue-tracking-rogvid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/rogvid/dotfiles/tree/main/opencode/.config/opencode/skill/issue-tracking
Command: npx skills add https://github.com/rogvid/dotfiles --skill issue-tracking-rogvid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Provides a lightweight, file-based issue tracking system that stores tickets as Markdown files with YAML frontmatter in a dedicated tasks/ directory, enabling teams to plan, track, and evolve work with a human-readable format and a minimal CLI.

Core Features & Use Cases

  • File-based tickets with rich metadata (id, status, type, priority, assignee, created, deps, links, tags) stored as Markdown.
  • Dependency management and simple workflows to model task relationships and progress.
  • Portable and Git-friendly: no database, just plain text files that can be versioned and merged.
  • Lightweight CLI (tk) to create, list, show, edit tickets, manage dependencies, and add notes for decisions and blockers.

Quick Start

Run scripts/tk create 'Sample issue' -t task -p 0 -d 'Describe the issue' to create a demo ticket in the tasks/ directory.

Frequently Asked Questions about issue-tracking

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

FAQPage Schema
How do I track issues and dependencies using Markdown files?

Track issues and dependencies by storing tickets as Markdown files with YAML frontmatter in a tasks/ directory. A portable CLI script manages the lifecycle, allowing you to create, list, edit, and link tickets directly from your terminal.

Can I use a file-based issue tracking system with Git for version control?

Yes, file-based issue tracking is Git-friendly. Tickets are stored as plain text Markdown files without a database, meaning your issue tracking data can be easily versioned, merged, and reviewed alongside your code changes.

What is the best way to manage ticket dependencies for a small team?

Manage ticket dependencies for a small team using a lightweight CLI that models task relationships. Tickets include standardized fields like deps and links, enabling simple workflows to track progress and visualize blockers within your Markdown files.

How do I create a new task ticket from the command line?

Create a new task ticket from the command line by executing the CLI script with arguments for title, type, priority, and description. This generates a Markdown file populated with YAML frontmatter metadata in your tasks/ directory.

What metadata fields are supported for Markdown tickets?

Markdown tickets support rich YAML frontmatter metadata including id, status, type, priority, assignee, created, deps, links, and tags. These standardized fields enable consistent lifecycle management and dependency tracking across your tasks.

When should I avoid using a lightweight file-based issue tracker?

Avoid using a file-based issue tracker if your team requires a centralized database, complex access control, or advanced reporting features. This lightweight system relies on plain text files and a CLI, making it ideal for small teams but limited for large-scale enterprise workflows.