t1k:watzup

Generate structured session progress reports from git history and task status.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-watzup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t1k:watzup
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/t1k-watzup
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-watzup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, cat, echo, TaskList, t1k:doctor, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The t1k:watzup Skill addresses the need for a streamlined session review process by summarizing session progress, including git history, task status, skill sync gaps, and test coverage. It provides a concise wrap-up to enhance productivity and facilitate better communication during standups.

Core Features & Use Cases

  • Session Progress Summary: Quickly summarize git history, task status, skill sync gaps, and test coverage for a session.
  • Live Context: Present recent commits, module summary, and task checks.
  • Regression Detection: Identify and alert on new error types or spikes in error counts across sessions.
  • Telemetry Review: Aggregate and review error patterns, skill usage, feature gaps, and hook diagnostics.
  • Output Format: Deliver a structured status report with actionable insights for the next steps.

Quick Start

Run the t1k:watzup Skill to generate a summary of your session progress.

Frequently Asked Questions about t1k:watzup

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

FAQPage Schema
How do I generate a session summary report from git history and task status?

To generate a session summary, you can automate the collection of git history, task status, skill sync gaps, and test coverage into a structured report. This provides a concise wrap-up to enhance productivity and facilitate communication during standups.

What is the best way to detect new error types or spikes across development sessions?

Detecting new error types or spikes involves reviewing telemetry and error patterns across sessions. This process identifies and alerts on regressions, aggregating error data to provide actionable insights for resolving issues in your next steps.

Can I use git commands to aggregate telemetry and review skill usage diagnostics?

Yes, you can utilize git commands and scripting to automate telemetry review. This approach aggregates error patterns, skill usage, feature gaps, and hook diagnostics, delivering a structured status report for your software development workflow.

Does session progress tracking require a specific environment setup before running?

Session progress tracking requires a software development environment with git installed. The analysis utilizes git commands, task lists, and scripting to extract recent commits, module summaries, and task checks for the structured report.

What should I do if my session progress summary is not capturing test coverage?

If your session summary is not capturing test coverage, verify that your testing framework outputs results accessible to the script. The automation relies on parsing local development artifacts to identify gaps and include them in the final structured status report.