Skip to content
Skills Library
Management & product · Analysis

github-weekly-report

/github-weekly-report

Generate comprehensive weekly activity reports for GitHub organizations showing merged PRs, open PR review status, new issues, CI health, active epics, and multi-repo contributor highlights with AI-synthesized Cross-Repo Highlights and Action Items. Use when the user wants a weekly summary, org activity report, "what happened this week" recap, or a GitHub org status update for a specific date range.

Repository
repoman ↗
Licence
Apache-2.0
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
2
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/epic-tracker.py, scripts/report.py

What it does and when to use it

Generate comprehensive weekly activity reports for GitHub organizations showing merged PRs, open PR review status, new issues, CI health, active epics, and multi-repo contributor highlights with AI-synthesized Cross-Repo Highlights and Action Items. Use when the user wants a weekly summary, org activity report, "what happened this week" recap, or a GitHub org status update for a specific date range.

Triggers from the description

what happened this week
Original author description

Generate comprehensive weekly activity reports for GitHub organizations showing merged PRs, open PR review status, new issues, CI health, active epics, and multi-repo contributor highlights with AI-synthesized Cross-Repo Highlights and Action Items. Use when the user wants a weekly summary, org activity report, "what happened this week" recap, or a GitHub org status update for a specific date range.

How it works

  1. Prerequisites
  2. Quick Start
  3. What the Report Includes
  4. Phase 2: AI Synthesis
  5. Automation
  6. See Also
Original SKILL.md headings · 146 lines, 1,214 words
SKILL.md preview
---
name: github-weekly-report
description: Generate comprehensive weekly activity reports for GitHub organizations showing merged PRs, open PR review status, new issues, CI health, active epics, and multi-repo contributor highlights with AI-synthesized Cross-Repo Highlights and Action Items. Use when the user wants a weekly summary, org activity report, "what happened this week" recap, or a GitHub org status update for a specific date range.
metadata: {"openclaw": {"requires": {"bins": ["gh", "python3"]}}}
---

# GitHub Weekly Report

Generate comprehensive weekly activity reports for GitHub organizations. Produces clean Markdown perfect for GitHub issues or documentation.

The report is produced in **two phases**:
1. **Phase 1 — Data collection** (`report.py`): fetches PRs, issues, CI runs, and active epics via the `gh` CLI and renders the mechanical sections.
2. **Phase 2 — AI synthesis** (you, the agent): reads the generated report and structured JSON, then writes the **Cross-Repo Highlights**, **Active Epics**, and **Action Items** sections using your own reasoning.

## Prerequisites

- **Python 3.8+**
- **GitHub CLI (`gh`)** — authenticated with access to the target org
- **Token scope**: `read:project` is optional — it only enriches the epic Status column from the Projects v2 board. Active-epic detection is sub-issue-based and works without it.

### Requirements (machine-readable)

- pat_scopes: [repo, read:org]
- labels_required: [epic]
- labels_applied: []
- programs: [report]

## Quick Start

```bash
# Report on current week (last 7 days) — also emit JSON for AI synthesis
python3 {baseDir}/scripts/report.py --org <org> --output report.md --json-output report-data.json

# Report on specific date range
python3 {baseDir}/scripts/report.py --org <org> --since 2026-03-23 --until 2026-03-30 --output report.md --json-output report-data.json

# Report on an explicit repo set (owner-qualified); skips org-wide discovery.
# --org is OPTIONAL here: each entry carries its own owner, so the set may span
# owners. A bare (unqualified) repo name still needs --org to supply its owner.
python3 {baseDir}/scripts/report.py --repos owner-a/repo-a owner-b/repo-b --output report.md --json-output report-data.json

# Run epic tracker standalone (for debugging)
python3 {baseDir}/scripts/epic-tracker.py --repos owner-a/repo-a owner-b/repo-b --since 2026-03-23 --until 2026-03-30

# Post report to a GitHub issue
gh issue create -R <org>/<repo> --title "Weekly Report $(date +%Y-%m-%d)" --body-file report.md
```

`--org` and `--repos` cover two modes. With `--org` and no `--repos`, the report discovers all repos in that org (the unchanged default). With an owner-qualified `--repos` set, `--org` is optional and the set may span multiple owners — each repo is fetched and linked under its own owner, and a report covering more than one owner skips the org-scoped Projects v2 status lookup (which has no single org to query) and falls back to activity-based epic detection. Automation deployments pass the curated, possibly multi-owner allowlist via the `weekly-report.sh` wrapper, which resolves the list and calls `report.py --repos owner/name …` for you.

## What the Report Includes

1. **Org-Wide Summary** — table with merged PRs, open PRs, open issues, new issues, CI pass rate, and status per repo
2. **Active Epics** — table of in-progress epics with leads, Key Results, and this-week activity
3. **Cross-Repo Highlights** — AI-synthesized narrative (see Phase 2 below)
4. **Per-Repo Deep Dives** — top contributors, merged PR table, open PRs by status (Ready to Merge / Changes Requested / Needs Review / Draft) with Notes flags, CI Health section, new issues
5. **Action Items** — AI-synthesized prioritized table (see Phase 2 below)

---

## Phase 2: AI Synthesis

After running `report.py`, read both the generated `report.md` and `report-data.json`. Use them to write three sections that require reasoning across the whole dataset.

### Active Epics

The script generates a baseline Active Epics table from `epic-tracker.py` output. Review it and enhance:

| Epic | Lead | Key Result | This Week |
|------|------|------------|-----------|
| [kagenti/kagenti#1789](https://github.com/kagenti/kagenti/issues/1789) OPA Authorization | @davidhadas | KR2: Zero-trust agent auth | 3 sub-issues closed, 4 open |
| [kagenti/kagenti-extensions#501](https://github.com/kagenti/kagenti-extensions/issues/501) Session Mgmt | @sahilsuneja1 | KR1: Stateful agent infra | 2 open, 1 PR merged |

Rules:
- Scan for the `epic` label across all repos in the org
- **Detection is sub-issue-based** (the primary signal): an epic is active if it has open sub-issues (backlog / in-progress) OR a sub-issue closed within the reporting window. This does not depend on the project board and needs no `read:project` scope. A merged-PR cross-reference in the window also counts.
- Board Status (Projects v2), when available, is **display-only enrichment** — it fills the status label but never gates inclusion. Teams often park active epics in an "Epics" column rather than "In Progress", so board status alone misses them.
- Lead = first assignee on the epic issue
- Epic reference = full `org/repo#N` with link to the source repo
- Key Result = extracted from epic body (`## Key Results` section) or inferred from title/labels
- "This Week" = brief summary of sub-issues closed / open, plus any PRs merged referencing this epic
- Cap the list (configurable via `--max-epics`, default 10); sort by recent activity (sub-issues closed this week, then open count) descending to keep the section a focused planning input
- If the script produced a fallback-mode table (no Projects v2 access), the status column is derived from sub-issue state — keep the section

### Cross-Repo Highlights

Replace the scaffold in `## Cross-Repo Highlights` with a rich narrative. Write bullet points covering **all** of the following that are relevant:

**Multi-repo contributors**
- For each person who merged PRs in more than one repo, describe *what* they worked on — not just a count. Name the repos and the themes.
- Call out the dominant contributor in the most active repo by name with a one-line summary of their impact.

**Org-wide CI narrative**
- State the overall org CI pass rate (compute as total passed / total runs across all repos).
- Call out which repos drag the average down and name the specific failing workflow(s).
- Highlight repos at 100% by name.

**Security concerns**
- List any open PRs flagged SECURITY that have been open >7 days without review. Link to the PR. Note the age.

**Dependabot accumulation**
- If the total open dependabot PRs across the org is significant (>10), call it out with a per-repo breakdown.

**Shared patterns / themes**
- Identify recurring themes across repos this week.

### Action Items

Append a `## Action Items` section at the end of the report. Produce a prioritized table of concrete actions.

**Priority criteria:**

| Priority | Criteria |
|----------|----------|
| **P0** | Security PRs unreviewed >7 days; CI broken on main for multiple consecutive days; active data/credential leak |
| **P1** | APPROVED PRs not yet merged; critical/regression bugs with no assignee; operator bugs causing pod restart loops |
| **P2** | PRs with CHANGES_REQUESTED where author has not responded >5 days; dependabot batch reviews; stale draft PRs blocking others |
| **P3** | Stale issues >30 days; ancient PRs >90 days with no review; quiet-repo triage; documentation gaps |

**Table format:**

```markdown
| # | Action | Repo | Owner | Priority |
|---|--------|------|-------|----------|
| 1 | Review and merge security fix #188 | agent-examples | @pdettori | P0 |
```

**Rules for Action Items:**
- Include only actionable items — skip things already in progress with healthy momentum
- Assign a named owner where obvious
- Limit to 15 items max, highest-priority first
- Reference GitHub issue/PR numbers with links

---

## Automation

The cron job runs weekly on Mondays at 05:01 UTC. The agent:
1. Runs `report.py` with `--json-output`
2. Reads the structured JSON and markdown
3. Enhances the Active Epics, Cross-Repo Highlights, and Action Items sections
4. Closes previous weekly report issues
5. Posts the final report as a new GitHub issue

Do not append a footer yourself. Leave any attribution line the report already has in place.

## See Also

- GitHub CLI docs: https://cli.github.com/manual/
- Example report: https://github.com/kagenti/kagenti/issues/1110
Files in this package (3)
  • SKILL.md 8 KB
  • scripts/epic-tracker.py 17 KB
  • scripts/report.py 25 KB

Versions

The database has no other skills named github-weekly-report.

Database snapshot: 13.11.2026 · package version 4017f40490d8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100weekly-update
    Write the weekly team update from the week's record, for the team or for a manager, client or board. Use for "write the weekly update", "weekly recap", "what did we get done this week", or "status report".
  • 86report-writer
    Write a weekly progress report from the repository's recent activity. Use when the user asks for a progress report, a weekly report, or a status write-up.
  • 100team-weekly-report
    Generate a weekly team status report combining JIRA and GitHub data. Fetches closed, open, stale, and blocked issues plus PR activity for each team member. Requires a team config YAML file with JIRA project, GitHub repos, and team member mappings. Use when the user asks for a…
  • 100weekly-status
    Weekly accomplishment report. Pulls from Jira, GitHub, Confluence, and Slack to produce a structured status report with accomplishments, metrics, blockers, and next week plan. Triggers on: "weekly status", "status report", "what did I do this week".
  • 85bops-130-write-the-weekly-status-report
    Write a one-page weekly status report from the record: headline, decisions needed, done, slipped, at risk, next week. Use when the owner asks for a status update, a weekly summary or a recap.
  • 86report-writer
    Write a weekly progress report from the repository's recent activity. Use when the user asks for a progress report, a weekly report, or a status write-up.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.