weekly-report

Generate weekly progress reports from commits, issues, and PRs.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AINative-Studio/telemetry-agent --skill weekly-report-ainative-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-report
Source: https://github.com/AINative-Studio/telemetry-agent/tree/main/.ainative/skills/weekly-report
Command: npx skills add https://github.com/AINative-Studio/telemetry-agent --skill weekly-report-ainative-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate standardized weekly progress reports by aggregating commits, issues, and PR signals across AINative repositories to provide a clear, shareable narrative.

Core Features & Use Cases

  • Executive Summary: High-level week-over-week status suitable for stakeholders.
  • Developer Velocity: Metrics on commits, issues closed, PRs merged, and trend analysis.
  • Major Features Implemented & Critical Bugs: Highlight key work and fixes with context.
  • Next Week Priorities: Planned focus areas and alignment across teams.

Quick Start

Run the weekly-report skill to generate a structured weekly progress report from the current repository state.

Frequently Asked Questions about weekly-report

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

FAQPage Schema
How do I generate a weekly progress report from git commits and PRs?

Generate a weekly progress report by analyzing repository commits, issues, and PRs to produce a structured Markdown document. The report aggregates signals across repositories to provide a clear, shareable narrative for sprint reviews and stakeholder updates.

What is developer velocity and how is it calculated for sprint reviews?

Developer velocity is calculated by analyzing metrics on commits, issues closed, and PRs merged to provide trend analysis for sprint reviews. The report aggregates these signals across repositories to measure team productivity and week-over-week progress.

Can I automate weekly report generation for stakeholder updates across multiple repositories?

Automate weekly report generation by aggregating commits, issues, and PR signals across AINative repositories. The skill produces a standardized Markdown report with an executive summary suitable for stakeholder updates and team retrospectives.

Does the weekly report include sections for critical bug fixes and infrastructure improvements?

The weekly report includes sections for critical bug fixes and infrastructure improvements alongside major features implemented. It also covers security improvements, frontend improvements, and work in progress to provide comprehensive project status.

What's the best way to track next week priorities in a standardized Markdown report?

Track next week priorities by generating a structured Markdown report that includes planned focus areas and team alignment. The report aggregates repository signals to document priorities alongside commit statistics and success metrics.

Do I need any specific dependencies or components to run the weekly report skill?

No specific dependencies or components are required to run the weekly report skill. Run the skill directly against the current repository state to analyze commits, issues, and PRs and produce a structured progress document.