github-work-rollup

Generate read-only GitHub work rollups and external-comment attention reports.

5|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill github-work-rollup-cbusillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-work-rollup
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/github-work-rollup
Command: npx skills add https://github.com/cbusillo/codex-skills --skill github-work-rollup-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve? Keeping track of active, blocked, stale, and completed work across many GitHub repositories is manual and error-prone, and external issue or PR comments often go unseen by the owner. This Skill collects read-only GitHub state and produces situational-awareness rollups plus reports of external comments that still need attention. ## Core Features & Use Cases - Work Rollups: Collect issues, PRs, releases, and workflow runs across repos or owners, bucketed by state (blocked, waiting, ready for review, stale, recently completed) with activity, backlog, and standup modes. - Audience Layouts: Render operator, manager, or executive briefs, including verified local-LLM synthesis grounded against evidence JSON. - External Comment Radar: Detect external issue/PR comments the owner has not seen or publicly addressed, distinguishing owner awareness from bot replies. - Use Case: Before a weekly leadership sync, run a standup-mode executive rollup across your org's repos to get a one-page brief of what shipped, what is blocked, and which external comments still need a reply. ## Quick Start Ask the agent to summarize my GitHub work over the last 24 hours across my repositories and flag any external comments I have not answered.

Frequently Asked Questions about github-work-rollup

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

FAQPage Schema
How do I generate a GitHub work summary across multiple repositories?

Run the rollup script with uv run scripts/github_work_rollup.py, passing --repo or --repo-owner flags plus a --window like 24h or 7d. It collects issues, PRs, releases, and workflow runs read-only and renders Markdown or JSON.

How can I find GitHub comments I have not replied to?

Use the unanswered-comments script with uv run scripts/github_unanswered_comments.py --repo-owner your-login. It reports external comments lacking an owner reaction or targeted reply, exiting 2 when attention is needed and 3 for degraded coverage.

Does this tool make any changes to my GitHub repositories?

No, the skill is strictly read-only in v1. It preflights GitHub access, collects state, and emits reports only; any write action such as commenting or merging is handed off to other skills or requires explicit user approval.

What is the difference between activity, backlog, and standup modes?

Activity mode shows only work changed inside the window, backlog mode includes all open work regardless of update time, and standup combines open backlog with recent activity and completions for working-session briefs.

Can I generate an executive brief from GitHub activity with a local LLM?

Yes, collect JSON evidence with --include-derived-context and --layout executive, then run synthesize_work_brief.py. It uses the prompt contract as the system prompt and verifies the brief against the evidence JSON.

Why does the rollup report say coverage may be incomplete?

Collection-limit safety ceilings cap PR, issue, release, and workflow rows per repo. When a ceiling is reached or an API lane fails, the report adds a source note stating the relevant counts may be incomplete.