Aggregate repository state into a start-of-session briefing with alerts.
npx skills add https://github.com/jellyrock/jellyrock --skill catchup-jellyrock
Please help me install this Agent Skill. Skill: catchup Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/catchup Command: npx skills add https://github.com/jellyrock/jellyrock --skill catchup-jellyrock
This Skill eliminates the tedious manual work of piecing together scattered repository state (git status, open PRs, CI runs, pending followups, upstream signal watchlists, and project journal staleness) at the start of a work session, ensuring you never miss urgent items or waste time reconstructing context after a gap.
Invoke the catchup skill at the start of any new work session to get a full repo state briefing with urgent alerts and a recommended next action.
High-intent search queries and answers about installing and using this skill.
To restore repository context at session start, you can aggregate scattered state like open PRs, CI run status, and pending followups into a single briefing. This eliminates manual context reconstruction by reading the project state cursor and watchlist to produce deterministic alerts.
Monitoring CI run status and project journal staleness is best handled by a single-call state aggregation script. It pulls all relevant repo state in one read, replacing dozens of manual git and file checks to automatically surface urgent items like stale progress docs.
Getting a start-of-session repo state briefing requires invoking a single aggregation command. The script reads the project's progress.md state cursor and signals-backlog.md watchlist, generating prioritized next-step suggestions and banner alerts without manual parsing.
Yes, tracking pending followups and repo state requires access to the project's catchup-state.js aggregator script, progress.md state cursor, signals-backlog.md watchlist, and ADR directory to produce deterministic banner alerts and next-step suggestions.
Yes, a session-start briefing can track upstream signal watchlists and pending PR reviews. The aggregation script consolidates this scattered repository state, automatically surfacing outdated upstream signals and pending reviews as urgent deterministic banner alerts.
Manual context reconstruction fails after time gaps because it requires piecing together scattered repository state like git status, open PRs, and CI runs. This tedious process risks missing urgent items, whereas a single-call state briefing aggregates all checks deterministically.
FrantssConfigure repository issue tracking, triage labels, and documentation layouts.
TMI-appsLoad DEVELOPMENT_PLAN.md, resolve the next pending phase, and execute its steps with gates.
jorgeasaurusConfigure persistent memory and observation feeds for OpenClaw gateways.
whilpTrigger and monitor GitHub Actions workflows via gh CLI.
