ac-report

Generate weekly or monthly Markdown reports from Git commit histories.

6|2|Updated Jan 9, 2026

Search Tags:#automation #git #templates #markdown #reporting #monthly #weekly

Ready to run

npx skills add https://github.com/yz0812/ai-dev-toolkit --skill ac-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ac-report
Source: https://github.com/yz0812/ai-dev-toolkit/tree/main/skills/ac-report
Command: npx skills add https://github.com/yz0812/ai-dev-toolkit --skill ac-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Weekly/monthly reporting from Git commits is tedious and error-prone.

Core Features & Use Cases

Automates generation of weekly and monthly reports from commit history across one or more repositories.
Supports MCP or local git log as data source, and fills templates to produce Markdown reports.
Useful for engineering teams to summarize activity for stakeholders or sprint reviews.

Quick Start

Run the /ac-report command to generate a weekly or monthly report from the current Git repository.

Frequently Asked Questions about ac-report

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

FAQPage Schema

How do I automate weekly report generation from Git commits?▼

Automate weekly report generation by running a command to read Git commit histories and populate templates. It outputs a Markdown report summarizing individual or team activity across one or multiple repositories for stakeholders.

Can I generate monthly Git reports across multiple repositories?▼

Yes, you can generate monthly Git reports across multiple repositories. The tool reads commit data via MCP or local git log, applies templates, and produces a consolidated Markdown report suitable for sprint reviews or stakeholder updates.

What is the best way to format Git commit logs into a Markdown report?▼

The best way to format Git commit logs into a Markdown report is using template-based automation. It extracts commit data via MCP or local git log and fills predefined templates located in assets to produce structured Markdown output.

Does this reporting tool support MCP as a data source for Git history?▼

Yes, the reporting tool supports MCP as a data source for Git history. It can read commit data via MCP or local git log, then apply templates to generate weekly or monthly Markdown reports for engineering teams.

Do I need local Git installed to generate monthly reports from commit history?▼

You do not strictly need local Git installed to generate monthly reports from commit history. The tool can read commit data via MCP as an alternative data source, populating templates to output a Markdown-ready report.