whats-up

Generates a TV-drama style session recap from git history, pull requests, and memory files.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill whats-up-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: whats-up
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/whats-up
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill whats-up-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Catching up on recent engineering work across multiple repositories requires manually checking git logs, open PRs, uncommitted changes, and personal notes. This Skill consolidates all of that into a single narrative recap so you can resume work quickly after time away. ## Core Features & Use Cases - Multi-repo context gathering: Pulls recent commits, open PRs with review status, and dirty working trees from both the Lumy-Backend and RG-Frontend repositories in parallel. - Memory and TODO integration: Reads persistent memory files and active todo lists to surface known blockers and in-flight work. - Structured narrative output: Produces a fixed three-section recap (Previously On, The Cliffhanger, What's On Deck) in under 200 words, scannable in 30 seconds. - Use Case: After a weekend away, ask "what's up" and receive a dramatic but factual summary of what shipped, what broke, which PRs await review, and the top action items. ## Quick Start Ask the assistant "what's up" or "catch me up on the ReallyGlobal project" to generate the session recap.

Frequently Asked Questions about whats-up

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

FAQPage Schema
How do I get a summary of recent work across multiple git repos?

Ask "what's up" or "catch me up" and the Skill runs git log, gh pr list, and git status across both configured repositories in parallel, then synthesizes the results into a short narrative recap with action items.

How to check open pull requests and review status with GitHub CLI?

The Skill runs gh pr list with JSON output for number, title, reviewDecision, and branch name in each repository. Open or unreviewed PRs are surfaced in the Cliffhanger section of the recap.

Does this recap work with repositories other than Lumy-Backend and RG-Frontend?

The Skill is hardcoded to those two repository paths and specific memory file locations. To use it elsewhere, you would need to edit the paths in SKILL.md to point at your own repositories.

What happens if there is no recent activity in the repos?

If the repos are clean, no PRs are open, and no todos exist, the Skill outputs a direct statement that the stack is running and the team is waiting on the next ticket, rather than fabricating a recap.

Why does the recap include uncommitted changes and memory files?

Git status reveals dirty or in-flight work that commits miss, and the memory and todos files capture blockers and plans that never appear in version control. Combining both gives a complete picture of project state.