weekly-synthesis

Name: weekly-synthesis
Availability: InStock
Author: Aakash

Scan git commits, group by folder, and generate Slack-ready weekly summaries.

32|16|Updated May 6, 2026

Search Tags:#slack #decision tracking #customer insights #git commits #repo health #weekly summary #analytics changes

Ready to run

npx skills add https://github.com/aakashg/product-growth-team-os --skill weekly-synthesis-aakashg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-synthesis
Source: https://github.com/aakashg/product-growth-team-os/tree/main/.claude/skills/weekly-synthesis
Command: npx skills add https://github.com/aakashg/product-growth-team-os --skill weekly-synthesis-aakashg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of teams losing visibility into what changed across the repo during the week, making it harder to prepare for standup, share decisions, and catch meaningful customer or metric updates.

Core Features & Use Cases

Weekly change scan & grouping: Reviews git commits from the last 7 days and groups changes by key folders (product, analytics, engineering, data-engineering, team) so updates stay organized and skimmable.
Decision, insight, and metric highlighting: Surfaces decisions logged, customer insights from calls or summaries, and metric or schema movements that impact planning.
Actionable Slack-ready output: Produces a formatted message suitable for posting to the team channel, including top items and repo health signals like file additions and contributors.

Quick Start

Run the weekly-synthesis skill to generate a Slack-ready summary of everything that changed in the Team OS repo over the last 7 days, grouped by folder.

Frequently Asked Questions about weekly-synthesis

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

FAQPage Schema

How do I generate a weekly summary of git commits for Slack?▼

You can generate a weekly Slack summary of git commits by scanning repository changes from the last 7 days, grouping them by folder, extracting decisions and customer insights, and formatting the output into a message under 500 words.

What is the best way to track repo changes and decisions for cross-team awareness?▼

Tracking repo changes and decisions for cross-team awareness involves scanning git commits weekly, grouping updates by key folders like product and engineering, and surfacing logged decisions and metric movements in a skimmable format.

How does grouping git commits by folder improve weekly reporting?▼

Grouping git commits by folder improves weekly reporting by organizing changes into distinct categories such as analytics, data-engineering, and team updates, making the summary skimmable and ensuring relevant context is easy to locate.

Can I extract customer insights and metric changes from git commit history?▼

Yes, you can extract customer insights and metric changes from git commit history by analyzing recent repository updates to surface decisions logged, customer call summaries, and schema or metric movements that impact planning.

Does the weekly summary output include repo health signals like contributors and file additions?▼

Yes, the weekly summary output includes repo health signals such as file additions and contributors, alongside top grouped changes, to provide a comprehensive view of repository activity for the team channel.

When should I run a weekly repo synthesis for Monday standup preparation?▼

You should run a weekly repo synthesis on Friday reporting cycles before Monday standup, ensuring cross-team visibility into product, engineering, and analytics changes made to the repository over the last 7 days.