github-weekly-summary

Generates weekly engineering reports from GitHub releases and Jira metrics for Notion and Discord.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/guizonatto/myopen-claw --skill github-weekly-summary-guizonatto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-weekly-summary
Source: https://github.com/guizonatto/myopen-claw/tree/main/skills/github-weekly-summary
Command: npx skills add https://github.com/guizonatto/myopen-claw --skill github-weekly-summary-guizonatto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, python-dotenv, openai, and includes scripts (resource) and references (resource) components.

What problem does it solve? Compiling weekly engineering status reports from GitHub releases, commits, and Jira issues is repetitive manual work. This Skill automates the entire pipeline: collecting data, computing delivery metrics (velocity, lead time, cycle time, WIP aging, rework), generating AI-written summaries in multiple formats, and publishing results to Notion and Discord. ## Core Features & Use Cases - Multi-source data collection: Fetches weekly releases and commits from multiple GitHub repositories and branches, plus Jira issues with full status-change history via the Jira REST API. - Engineering metrics: Computes weekly throughput, lead time p50/p85, cycle time, queue time, flow efficiency, deploy lag, WIP aging, and rework breakdown, rendered as ASCII charts for Discord. - AI-generated summaries: Produces FAQ (sales/support and end-user), CEO executive summary, Discord message, email, RAG-indexable text, and a structured Notion page payload via an LLM. - Automated distribution: Creates a Notion database page per release and posts the report to a Discord channel, optionally inside a weekly thread. - Use Case: A tech lead runs the pipeline every Friday to publish a weekly report thread in Discord with velocity charts and a Notion changelog page, without writing anything by hand. ## Quick Start Set the required environment variables for GitHub, Jira, Notion, and Discord, then run python skills/github-weekly-summary/scripts/main.py to generate and publish the weekly report.

Frequently Asked Questions about github-weekly-summary

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

FAQPage Schema
How do I generate a weekly report from GitHub and Jira automatically?

Configure the required environment variables (GITHUB_TOKEN, GITHUB_REPO, JIRA_EMAIL, JIRA_TOKEN, JIRA_BASE_URL, JIRA_PROJECT_KEY, NOTION_TOKEN, NOTION_DATABASE_ID, DISCORD_BOT_TOKEN, DISCORD_GUILD_ID), then run scripts/main.py. The pipeline fetches data, generates AI summaries, exports to Notion, and posts to Discord.

What engineering metrics does this Jira reporting pipeline calculate?

It computes weekly throughput with trend detection, lead time and cycle time percentiles (p50/p85), queue time, flow efficiency, deploy lag, WIP aging by risk level, time-in-status averages, and rework breakdown by transition type such as review or QA rejections.

Can I send the weekly report to a specific Discord channel or thread?

Yes. Set DISCORD_CHANNEL_ID or GITHUB_WEEKLY_DISCORD_CHANNEL_ID to target a channel directly. Otherwise the script scans server channels and picks one matching keywords like weekly-report, releases, or changelog, and creates a thread titled with the week number.

Why does the pipeline fail with a missing environment variable error?

The main script validates all required variables before running and exits listing the missing ones. Check that every GitHub, Jira, Notion, and Discord credential is set in your .env file, and confirm tokens have the correct API permissions.

Does this skill use web search or browser tools for data collection?

No. The skill operates exclusively through the GitHub, Jira, Notion, and Discord APIs plus local scripts. Web search or browser tools are only a fallback for exceptional API failures, not part of the standard flow.

What summary formats can the AI generate for weekly releases?

The summarization step produces a sales/support FAQ, an end-user FAQ, a CEO executive summary with metrics, a short Discord message, a formatted email, RAG-indexable text for AI search, and a structured Notion page payload with properties and children blocks.