weekly-summary

Generate weekly GitHub progress summaries and post them to Slack.

93|23|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/RConsortium/pharma-skills --skill weekly-summary-rconsortium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-summary
Source: https://github.com/RConsortium/pharma-skills/tree/main/_automation/weekly-summary
Command: npx skills add https://github.com/RConsortium/pharma-skills --skill weekly-summary-rconsortium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, github-api, slack-api, and includes scripts (resource) and config (resource) components.

What problem does it solve?

This Skill automates the generation of weekly progress summaries for a specified repository, providing a developer-focused update in Slack and saving the summary as a markdown file.

Core Features & Use Cases

  • Automated Summary Generation: Summarizes recent commits, PRs, and issues for a specified lookback period.
  • Slack Posting: Posts the summary to a designated Slack channel.
  • Markdown File Creation: Saves the summary as a markdown file for future reference.
  • Use Case: Use this Skill to keep your team informed about the latest developments in your repository, without manual updates.

Quick Start

Use the weekly-summary skill to generate a weekly summary for the pharma_skills repository and post it to the #development channel.

Frequently Asked Questions about weekly-summary

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

FAQPage Schema
How do I automate weekly GitHub repository summaries for Slack?

Automating weekly GitHub repository summaries for Slack involves fetching recent commits, pull requests, and issues via the GitHub API, formatting them into a concise update, and posting it to a designated Slack channel using the Slack API.

What is included in a developer weekly report for a GitHub repository?

A developer weekly report for a GitHub repository includes a concise summary of recent commits, pull requests, and issues from a specified lookback period, providing a focused update on repository progress.

Do I need GitHub and Slack API access to generate repository progress updates?

Yes, you need GitHub and Slack API access to generate repository progress updates, as GitHub API provides the commit, PR, and issue data while Slack API is required to post the summary to a channel.

Can I save a GitHub weekly summary as a markdown file instead of posting to Slack?

Yes, the GitHub weekly summary process saves the generated update as a markdown file for future reference in addition to posting it to Slack, ensuring you have a persistent record of repository progress.

What's the best way to keep my team informed about recent GitHub commits and pull requests?

The best way to keep your team informed about recent GitHub commits and pull requests is to automate a weekly progress summary that aggregates repository activity and posts a concise developer update directly to Slack.