weekly-report

Generate weekly progress reports from git commits, issues, and pull requests.

2|1|Updated May 27, 2025

Search Tags:#automation #git #code analysis #github #reporting #developer productivity

Ready to run

npx skills add https://github.com/PAIPalooza/chicommerce --skill weekly-report-paipalooza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-report
Source: https://github.com/PAIPalooza/chicommerce/tree/main/.ainative/skills/weekly-report
Command: npx skills add https://github.com/PAIPalooza/chicommerce --skill weekly-report-paipalooza

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of comprehensive weekly progress reports by analyzing Git commits, GitHub issues, and pull requests, saving developers significant time on administrative tasks.

Core Features & Use Cases

Automated Data Aggregation: Gathers commits, issues, and PRs across specified repositories.
Developer Velocity Tracking: Calculates metrics like commit counts, issues closed, and PRs merged to assess productivity.
Structured Reporting: Organizes findings into a standardized Markdown report with sections for executive summary, velocity, features, fixes, and future priorities.
Use Case: At the end of each week, you can run this Skill to generate a detailed report of your contributions, which can then be shared with your team lead or used for personal tracking.

Quick Start

Use the weekly-report skill to generate your progress report for the past week.

Frequently Asked Questions about weekly-report

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

FAQPage Schema

How do I automate developer progress reports from git commits and GitHub issues?▼

Automating developer progress reports involves analyzing git commits, GitHub issues, and pull requests across multiple repositories to calculate velocity and summarize implemented features. This generates a structured Markdown report tracking weekly contributions and future priorities.

What is developer velocity tracking and how does it summarize bug fixes?▼

Developer velocity tracking calculates metrics like commit counts, issues closed, and PRs merged to assess productivity. It analyzes git history to summarize implemented bug fixes, security improvements, and infrastructure changes into a structured report.

Can I generate a weekly progress report across multiple GitHub repositories?▼

Yes, you can generate a weekly progress report across multiple GitHub repositories. Automated data aggregation gathers commits, issues, and PRs from specified repositories to produce a unified structured Markdown report.

What is the best way to track work in progress and next week's priorities from pull requests?▼

The best way to track work in progress and next week's priorities from pull requests is by analyzing open PRs and recent git commits. This identifies active development threads and outlines future tasks within a structured Markdown report.

How do I calculate developer productivity metrics from git and GitHub data?▼

You calculate developer productivity metrics by aggregating git commits, GitHub issues, and merged pull requests across repositories. This computes velocity metrics and generates a structured Markdown report detailing your development output.