report-generator

To generate a weekly status report from git history and activity logs, this Skill automates data aggregation to compile completed tasks, code commits, and noted blockers into a structured summary. It ensures all report claims are traceable to their original data sources.

Yes, you can automatically create a retrospective report from project activity logs. The Skill supports various report types including incident reports and retrospectives, aggregating historical data to provide an evidence-based project overview.

Automated report generation works without manual data entry by directly pulling information from connected data sources. It aggregates evidence from git commits and activity records to ensure all claims are accurate and verifiable.

The best way to ensure project summary claims are traceable to data sources is to use an evidence-based report generator. This Skill links every claim in your project overview directly to underlying git history and activity logs.

Yes, you need the activity-logger and work-log-analyzer dependencies to generate incident reports. These components provide the necessary raw activity logs and analytical data required to produce accurate, evidence-based outputs.

Using an evidence-based report generator instead of manually writing a monthly summary prevents inaccuracies from memory gaps. It automatically aggregates git history and activity logs to ensure every claim is verifiable.