repo-pulse

Monitor GitHub repositories for daily stars, forks, and releases.

Updated Jun 2, 2026

Search Tags:#monitoring #github #notifications #releases #forks #stars #repo-pulse

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill repo-pulse-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-pulse
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/repo-pulse
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill repo-pulse-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates daily monitoring of watched GitHub repositories to surface new stars, forks, and releases with an enrichment layer and a growth verdict.

Core Features & Use Cases

Tracks activity for configured watched repos and filters out agent repos.
Aggregates 24h activity and historical deltas from memory logs to produce a concise pulse and verdict.
Generates notifications when activity exceeds thresholds and logs results for later analysis.

Quick Start

Run the repo-pulse skill daily to generate a summary of activity for watched repositories.

Frequently Asked Questions about repo-pulse

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

FAQPage Schema

How do I monitor daily GitHub repository activity for stars, forks, and releases?▼

Daily GitHub repository monitoring is automated by tracking watched repos via the Events API to surface new stars, forks, and releases. It aggregates 24h activity and historical deltas from memory logs to produce a concise pulse and growth verdict.

How do I get notifications when a watched GitHub repo gains new stars or forks?▼

Notifications for new stars or forks are generated conditionally when daily GitHub repository activity exceeds configured thresholds. The monitoring process evaluates 24h Events API data against these limits and triggers alerts while logging results for analysis.

What is a growth verdict in the context of GitHub repo monitoring?▼

A growth verdict is a computed summary derived from comparing 24h GitHub repository activity against historical counts from memory logs. It enriches raw star, fork, and release deltas to provide an actionable assessment of repository momentum.

Can I exclude specific agent repositories from my daily GitHub monitoring pulse?▼

Yes, agent repositories are automatically filtered out and excluded from the daily GitHub monitoring pulse. The tracking mechanism applies exclusively to your configured watched repos to ensure activity data remains relevant.

Does automated GitHub repo monitoring avoid exposing sensitive data in activity logs?▼

Automated GitHub repo monitoring avoids sensitive data exposure during the collection and logging processes. It safely aggregates public star, fork, and release events from the Events API into memory logs for delta computation.

What's the best way to track historical changes in GitHub repository stars and forks?▼

Tracking historical changes in GitHub stars and forks is best handled by logging daily Events API counts to memory logs. This allows the monitoring process to compute historical deltas and compare them against current 24h activity for accurate trend analysis.