weekly-commits

Aggregate git commit history into structured markdown reports by timeframe and author.

1|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hicucu/my-poor-ai --skill weekly-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-commits
Source: https://github.com/hicucu/my-poor-ai/tree/main/skills/weekly-commits
Command: npx skills add https://github.com/hicucu/my-poor-ai --skill weekly-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the difficulty of manually tracking and summarizing weekly development progress, ensuring clear visibility into work done across repositories and projects.

Core Features & Use Cases

  • Automated Summarization: Aggregates git commits into a clean, readable markdown table and a synthesized summary of work.
  • Monorepo Support: Automatically detects project structures and categorizes commits by sub-project.
  • Use Case: Use this at the end of the week to generate a professional report of your contributions for team updates or personal review without manually checking git logs.

Quick Start

Ask the assistant to show your work for the current week by typing weekly commits.

Frequently Asked Questions about weekly-commits

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

FAQPage Schema
How do I generate a weekly git commits summary for a team update?

To generate a weekly git commits summary, this skill aggregates local repository commit history into a structured markdown table and a synthesized report of your work. It automatically categorizes your contributions for the specified timeframe.

Can I automatically summarize commit history in a monorepo by sub-project?

Yes, you can automatically summarize commit history in a monorepo by sub-project. This skill detects monorepo project structures and categorizes commits accordingly, ensuring each sub-project's progress is clearly separated in the final markdown report.

Do I need python3 or node installed to parse git logs for reports?

Yes, you need either python3 or node installed to parse git logs for reports. This skill requires git alongside one of these runtime environments to read local commit history and generate the categorized markdown summaries.

What is the best way to track development progress across local git repositories?

The best way to track development progress across local git repositories is automating commit summarization. This skill parses git logs to identify work patterns and outputs clean, readable markdown reports without requiring manual log checking.

How does automated commit reporting handle authors and specific timeframes?

Automated commit reporting handles authors and specific timeframes by filtering local git commit history based on your requested parameters. This skill aggregates the matching commits into a structured markdown table and a synthesized summary of the work completed.

Are there limitations when generating weekly commit summaries from local git repositories?

A limitation when generating weekly commit summaries is that this skill operates strictly on local git repositories and requires git plus python3 or node to parse logs. It cannot fetch remote commit history or generate reports without these local dependencies installed.