Automate a weekly GitHub stars and activity report for your repos

Stars are a rough signal of attention, not usage. Still, a jump after a post or a launch tells you which channel worked, and a quiet stretch tells you the project needs a push. The count on a repository page is a snapshot; to see change you need last week's number, which nobody writes down. The job is to write it down for you and say what moved.

You list the public repositories to track. Each Monday a scheduled agent reads each repository's star count and open issue count through the GitHub repository endpoint, counts commits since the previous report with the list commits endpoint, and checks for a new release. It compares the numbers with last week's report and shows the change in stars, new releases, commits and open issues. If last week's report is not available, it records a baseline, so growth appears from the second week. It reads public data and writes nothing to GitHub.

The CMO agent, as department head, reviews the report before it reaches you: do the changes match last week's figures, is a spike explained by a known launch or post, is anything compared against the wrong week. Then you approve, edit or skip it, and nothing is sent until you do. The report does not say who starred or why, so it will not guess at causes; add a note when you know of one.

Pair a spike with what you published that week and write it in the launch or post notes field. After a month you will see which posts, directories or mentions moved the number and which did nothing. Keep the list short, a handful of repositories, so each line gets read. A repository that never moves is useful information too: it tells you where promotion has not landed yet.