stats

Report workflow progress, duration, and git metrics for tickets via Bash.

Updated Feb 25, 2026

Search Tags:#ticket tracking #work management #ticket analysis #git metrics #workflow statistics

Ready to run

npx skills add https://github.com/thomfilg/ai-plugin-work --skill stats-thomfilg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stats
Source: https://github.com/thomfilg/ai-plugin-work/tree/main/plugins/work/skills/stats
Command: npx skills add https://github.com/thomfilg/ai-plugin-work --skill stats-thomfilg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides quick insights into the workflow progress, duration, and git metrics for individual tickets or all tickets in the system.

Core Features & Use Cases

Workflow Progress Reporting: Display the current step position, the number of completed and remaining steps in a ticket.
Duration Calculation: Calculate the elapsed time for the ticket workflow.
Retry/Loop Count: Track the number of times the ticket has retried or looped.
Git Metrics: Provide git commit count and lines added/removed for the ticket branch.
Use Case: Use this Skill to get a high-level overview of ticket progress or to pinpoint bottlenecks or issues in the workflow.

Quick Start

Execute the 'stats PROJ-856' command to retrieve statistics for a specific ticket 'PROJ-856'.

Frequently Asked Questions about stats

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

FAQPage Schema

How do I track workflow progress and duration for a specific ticket?▼

Track workflow progress and duration by running a bash command with the ticket ID to report the current step position, completed steps, remaining steps, and elapsed time.

Can I retrieve git commit metrics for a specific ticket branch?▼

Yes, retrieve git commit metrics by analyzing the ticket branch to provide commit count and lines added or removed directly from the repository data.

Do I need node and git installed to analyze ticket statistics?▼

Yes, you need the node runtime to execute the analysis scripts and git installed to retrieve repository data for generating ticket workflow statistics.

How do I get aggregate workflow statistics for all tickets in the system?▼

Get aggregate workflow statistics for all tickets by running the stats command without a specific ticket ID to calculate overall duration, retry counts, and git metrics.

What is the best way to identify workflow bottlenecks using ticket statistics?▼

Identify workflow bottlenecks by analyzing ticket statistics to pinpoint high retry or loop counts, long elapsed durations, and abnormal git commit metrics across the system.

Can I track the number of times a ticket has retried or looped in the workflow?▼

Yes, track the number of times a ticket has retried or looped by running the stats command to retrieve the retry and loop count for that specific ticket.