Create Gitoxide monthly report outlines from GitHub and local git activity. Use when Byron asks for gh-monthly, a Gitoxide monthly report outline, or preparation for the report usually created around the 22nd. The skill uses `gh` to inspect all GitHub activity since the prior report or its last covered release, reads `/Users/byron/dev/github.com/GitoxideLabs/gitoxide` for git history and `etc/reports` samples, and incorporates must-include topics with summaries of how they were covered in the prior report.
Create Gitoxide monthly report outlines from GitHub and local git activity. Use when Byron asks for gh-monthly, a Gitoxide monthly report outline, or preparation for the report usually created around the 22nd. The skill uses `gh` to inspect all GitHub activity since the prior report or its last covered release, reads `/Users/byron/dev/github.com/GitoxideLabs/gitoxide` for git history and `etc/reports` samples, and incorporates must-include topics with summaries of how they were covered in the prior report.
GH Monthly
Create an outline for a Gitoxide monthly report. Produce a full draft only if explicitly asked.
Defaults
The Gitoxide checkout is /Users/byron/dev/github.com/GitoxideLabs/gitoxide.
Byron usually creates the report around the 22nd of each month.
If the target month is not specified, outline the current report month.
The reporting window starts immediately after the prior report's effective cutoff and ends at the current cutoff, usually today around the 22nd.
If the prior cutoff is unclear, use the latest project release covered by the prior report, even when it was published after the nominal report date. Treat its publication timestamp as an exclusive lower bound so neither that release nor its release activity is repeated in the new report.
Release data is boundary bookkeeping, not report material. Do not add release sections, tag lists, or version rollups unless Byron explicitly asks for them.
Target report path is etc/reports/YY-MM.md.
Use etc/reports as the style and structure reference.
Inputs
The user may provide must-include topics. Treat them as required sections or subsections unless they clearly belong together.
For each topic, preserve:
topic name
why it matters this month
what was written about it in the prior month
links, PRs, issues, contributors, or rough notes
Do not ask for topics. If none are provided, infer topics from GitHub and git activity.
Data Gathering
Run all commands from the local checkout unless another path is explicitly provided:
cd /Users/byron/dev/github.com/GitoxideLabs/gitoxide
Use exact timestamp bounds when available and state them in the outline. For the August 2026 report, if the prior report's last covered release is v0.56.0 at 2026-07-23T13:24:10Z, inspect activity strictly after that instant through the August 22 query time; do not include the v0.56.0 release wave. GitHub date qualifiers are inclusive and day-granular, so fetch timestamps in JSON and filter boundary-day results locally when necessary.
Use gh to inspect repository-wide GitHub activity, not only Byron's activity:
gh pr list --repo GitoxideLabs/gitoxide --state all --limit 200 --search 'updated:YYYY-MM-DD..YYYY-MM-DD'
gh issue list --repo GitoxideLabs/gitoxide --state all --limit 200 --search 'updated:YYYY-MM-DD..YYYY-MM-DD'
gh release list --repo GitoxideLabs/gitoxide --limit 20
For promising PRs and issues, inspect details instead of relying on titles:
gh pr view NUMBER --repo GitoxideLabs/gitoxide --comments --json title,body,state,author,mergedAt,closedAt,createdAt,updatedAt,additions,deletions,changedFiles,labels,reviews,comments,files,url
gh issue view NUMBER --repo GitoxideLabs/gitoxide --comments --json title,body,state,author,closedAt,createdAt,updatedAt,labels,comments,url
Use local git history to cross-check activity, find commits that did not surface clearly in PR listings, and understand touched areas:
