tk-triage

Triage stalled tk tickets using timestamps, ralph logs, and git data.

5|4|Updated Dec 4, 2017
One-click install
npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill tk-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tk-triage
Source: https://github.com/Nathan-Schwartz/dotfiles/tree/main/claude/.claude/skills/tk-triage
Command: npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill tk-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage stalled tk tickets by surfacing abandonment and in-progress work, collecting timestamps and ralph logs to understand why work stalled and what to do next.

Core Features & Use Cases

  • Surface Open / In-Progress and Abandoned tickets for quick review.
  • Gather per-ticket context (status, timestamps, git commits, and Ralph logs) to inform decisions.
  • Generate structured triage reports with recommended next steps and potential downstream impacts.

Quick Start

Run the tk-triage workflow on your ticket set to generate a structured triage report.

Frequently Asked Questions about tk-triage

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

FAQPage Schema
How do I triage stalled tickets to find out why work stopped?

Triage stalled tickets by surfacing abandonment and in-progress work, collecting timestamps and ralph logs to understand why work stalled and generate reports with recommended next steps.

What is the best way to classify open and abandoned tickets for review?

Classify open, in-progress, and abandoned tickets by gathering per-ticket context including status, timestamps, git commits, and Ralph logs to inform decisions and propose next steps.

Do I need a local tk toolchain to run ticket triage workflows?

Yes, ticket triage requires a local tk toolchain and access to git, ralph logs, and relevant ticket data to identify failure modes, classify issues, and propose next steps.

How do I generate a structured triage report with dependency impact analysis?

Generate structured triage reports with recommended next steps and potential downstream dependency impacts by operating across open, in-progress, and abandoned tickets to produce per-ticket reports and aggregate metrics.

Can I use git commits and ralph logs to identify ticket failure modes?

Yes, use git commits and ralph logs to identify failure modes, classify issues, and surface abandonment with timestamps to understand why work stalled and what to do next.

What are the limitations of automated issue classification for stalled tickets?

Automated issue classification depends on local access to git, ralph logs, and ticket data, meaning it cannot operate in isolated environments without these dependencies to identify failure modes.