github-monitor_skill

Overview

This skill monitors public GitHub repositories for new projects, significant updates, and star milestones, then drafts Reddit and Twitter posts for your approval before publishing. It prioritizes authentic, technical copy in first-person and never auto-posts without explicit user consent. It is designed for founders, indie hackers, and growth engineers who want consistent social distribution of real product work.

How this skill works

The agent fetches your recent repos and push history via the GitHub API and compares results against a stored state file. Triggers include newly created repos, repo pushes with >=3 new commits, and star milestone crossings. When triggered, it reads README, recent commits, and repo metadata to generate a Reddit post (structured problem / what I built / how it works / learnings) and a 1–3 tweet Twitter draft, then sends the drafts to you for approval.

When to use it

• Automatically monitor your GitHub account for new projects and major updates.
• Generate ready-to-edit social drafts when a repo gets significant new commits.
• Get notified when repositories cross star milestones so you can celebrate publicly.
• Keep an archive of published posts and maintain a baseline snapshot of repos.
• Run on a schedule (3x daily) or trigger manually with phrases like “check my github”.

Best practices

• Set GITHUB_USERNAME as an env var or in the state file before running.
• Run an initial sync to baseline all public repos; first sync does not notify.
• Review and edit drafts—never rely on automatic posting; reply with explicit commands to publish.
• Keep README and commit messages informative to improve draft quality.
• Record published URLs and milestones in the state file to avoid duplicate notifications.

Example use cases

• A solo founder launches a new side project repo and gets a ready Reddit post and tweet thread drafted for review.
• An engineer lands a substantial release with multiple commits; the skill drafts a technical update highlighting key changes.
• An open-source maintainer crosses a star milestone and receives a celebratory draft to share progress with the community.
• An indie hacker wants daily monitoring and heartbeat messages when nothing new is found.
• A growth engineer uses the drafts as a starting point for coordinated social campaigns across Reddit and Twitter.