Agent skill · writing content · rysweet
gh-work-report
Generates comprehensive GitHub activity reports across all authenticated accounts. Gathers repos, PRs, features, and themes for configurable time periods (1/5/7/30/90 days). Produces shareable markdown with tables, mermaid charts, and executive summaries. Can create a private repo with GitHub Actions automation and GitHub Pages aggregation site. Use when: "github report", "work report", "activity summary", "what did I work on", "gh-work-report", "show my github activity".
Why this skill is useful
Adds specific commands and workflows for generating GitHub activity reports that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-07-26. 71 stars on the source repository.
What this skill does
GitHub Work Report Skill Generates rich GitHub activity reports across all authenticated gh accounts. Invocation The user triggers this skill with phrases like: /gh-work-report (default: last 7 days) /gh-work-report show me the last 30 days generate a github work report for the last 90 days what did I work on this week Parse the time period Extract the number of days from the user's message. Valid values: 1, 5, 7, 30, 90. Default to 7 if not specified or if an invalid value is given. Workflow Follow these steps in order. Check off each step as you complete it. Step 1: Detect accounts Parse the output to identify all authenticated accounts (e.g., rysweet on github.com, rysweetmicrosoft on github.com). Store the list of account values and note which is currently active. Step 2: Gather data per account For each account, switch to it and collect data: Then gather: 2a. Repositories with recent activity Filter to repos with pushedAt within the time window. 2b. Pull requests Also gather PRs merged (not just created) in the window: Deduplicate by URL. 2c. Issues 2d. Releases Step 3: Combine and deduplicate Merge data from all accounts. Deduplicate repos by nameWithOwner and PRs by URL. Tag each item with the account that produced it. Step 4: Analyze and synthesize This is where you add value beyond raw data: 1. Identify themes: Group repos/PRs by topic (e.g., "infrastructure", "security", "new features"). Use repo descriptions, PR titles, and any patterns you observe. 2. Highlight big wins: PRs with significant impact — large features merged, important bug fixes, new repos created. 3. Extract usage examples: For notable features, write a short "here's how to use this" snippet based on PR titles, descriptions, and repo READMEs. 4. Spot new work: Repos with first-ever commits in the time window. Step 5: Generate the report Use the template structure from reference.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rysweet/gh_work_report