oat-wrap-up

Generate weekly wrap-up reports from OAT summaries and GitHub PR metadata.

Updated May 6, 2026

Search Tags:#git #github #weekly report #project summary #oat

Ready to run

npx skills add https://github.com/tkstang/skills --skill oat-wrap-up

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oat-wrap-up
Source: https://github.com/tkstang/skills/tree/main/.agents/skills/oat-wrap-up
Command: npx skills add https://github.com/tkstang/skills --skill oat-wrap-up

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of a weekly wrap-up report summarizing OAT projects and merged PRs, streamlining the process of tracking team accomplishments.

Core Features & Use Cases

Automatic Summary Generation: Automatically reads local summary files and GitHub PR metadata to synthesize a shipping digest.
Customizable Time Frames: Supports specifying a time window for the report using various date formats and ranges.
Version Control Integration: Writes the report to a version-controlled directory or outputs to stdout with a dry run.

Quick Start

Run /oat-wrap-up --past-week to generate a wrap-up report for the past week.

Frequently Asked Questions about oat-wrap-up

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

FAQPage Schema

How do I automate a weekly wrap-up report for GitHub PRs and local project summaries?▼

You can automate a weekly wrap-up report by using a tool that reads local OAT project summary files alongside GitHub PR metadata to synthesize a shipping digest. This process integrates with version control systems to generate the report automatically.

Can I specify a custom date range when generating a project summary?▼

Yes, you can specify a custom date range for your project summary by providing various date formats and ranges as input. This allows the report generation tool to filter GitHub PR metadata and local summaries within that exact time window.

Do I need the GitHub CLI installed to fetch merged PR metadata for reporting?▼

Yes, you need the GitHub CLI (`gh`) installed because the reporting tool relies on it to access the GitHub API and fetch merged PR metadata. This dependency is required to automatically pull repository data for the wrap-up report.

What is the best way to output a weekly report to a version-controlled directory?▼

The best way to output the weekly report is to use a tool that writes the synthesized GitHub PR and project summary directly to a version-controlled directory. Alternatively, you can perform a dry run that outputs the report to stdout without writing files.

Does this GitHub PR reporting tool work without an existing OAT project repository structure?▼

No, this GitHub PR reporting tool requires an existing OAT project repository structure to function correctly. It relies on reading the local summary files within that specific directory structure to synthesize the weekly wrap-up report.

Why does my automated weekly report fail to fetch GitHub PR metadata?▼

Your automated weekly report might fail to fetch GitHub PR metadata if the `gh` dependency is missing or lacks proper API access. Ensure the GitHub CLI is installed and authenticated so the tool can successfully read repository data.