repo-pulse

Aggregate stargazers, forks, and releases from watched GitHub repos into daily pulse reports.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill repo-pulse-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-pulse
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/repo-pulse
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill repo-pulse-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily progress signals for watched GitHub repos by automatically summarizing new stars, forks, and releases, plus enrichment of notable stargazers and a concise growth verdict.

Core Features & Use Cases

  • Automated daily repository pulse for watched repos.
  • Notable-stargazer enrichment and a one-line growth verdict.
  • Optional notification triggers when activity occurs.

Quick Start

Run this skill daily to generate a concise repo pulse for your watched repos.

Frequently Asked Questions about repo-pulse

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

FAQPage Schema
How do I automate daily GitHub repository monitoring for stargazers and releases?

Automate daily GitHub repository monitoring by aggregating stargazers, forks, and releases into a concise daily pulse report. This skill reads your watched repos list, processes GitHub API events, and logs daily results with a one-line growth verdict.

Can I get notifications when watched GitHub repos have new activity?

Yes, you can get notifications when watched GitHub repos have new activity. The daily pulse reporting process triggers notifications automatically when repository events like new stars, forks, or releases are detected via the GitHub API.

What is the best way to track notable stargazers for my GitHub repositories?

Track notable stargazers by applying enrichment to the daily repository pulse report. The skill aggregates stargazer data from the GitHub API and enriches the daily summary with contributor details alongside the standard growth verdict.

Do I need to configure a watched repositories list before generating a repo pulse?

Yes, you need a watched repositories list configured before generating a repo pulse. The skill reads from the memory/watched-repos.md file to identify which GitHub repositories to aggregate stargazers, forks, and releases data for.

How does daily repository pulse reporting handle growth analysis for multiple repos?

Daily repository pulse reporting handles multiple repos by reading the watched repositories list, aggregating stars, forks, and releases via the GitHub API, and producing a compact growth verdict for each repo with results logged to memory logs.

Are there limitations to automating GitHub repo monitoring with this pulse approach?

Limitations include dependency on GitHub API rate limits for aggregating stargazers and releases, and the requirement to manually maintain the watched-repos.md file. The daily pulse reporting is designed for a defined set of watched repositories rather than arbitrary dynamic discovery.