daily-report

Aggregate logs, TODO items, and git history into daily work reports.

Updated Aug 23, 2026

Search Tags:#automation #documentation #reporting #management #worklog #daily-report #git-log

Ready to run

npx skills add https://github.com/barikata1984/.claude --skill daily-report-barikata1984

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: daily-report
Source: https://github.com/barikata1984/.claude/tree/main/skills/daily-report
Command: npx skills add https://github.com/barikata1984/.claude --skill daily-report-barikata1984

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of a structured daily work report by aggregating data from docs/LOGS/, docs/TODO.md, and the git history, and outputs the result to docs/REPORTS/.

Core Features & Use Cases

Automated compilation of daily work items from logs and TODOs
Contextualizes work with relevant git history for the day
Saves the final report to docs/REPORTS/ for management review
Triggered by /daily-report or /daily-report YYYY-MM-DD to target a specific date

Quick Start

Invoke /daily-report to generate today's report, or use /daily-report YYYY-MM-DD to target a specific date.

Frequently Asked Questions about daily-report

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

FAQPage Schema

How do I automate daily report generation from git logs and TODO files?▼

Automating daily report generation aggregates logs from docs/LOGS/, docs/TODO.md, and git history into a management-ready document. The compiled report is automatically saved to docs/REPORTS/ for immediate review.

Can I generate a work report for a specific past date instead of today?▼

You can generate a work report for a specific past date by providing an optional YYYY-MM-DD parameter. This targets the git history and logs from that exact date to compile the correct daily activities.

What is the best way to compile development progress from multiple sources into one document?▼

Compiling development progress into one document is best handled by aggregating work logs, TODO items, and git history. This contextualizes daily code commits with tracked tasks to produce a structured daily report.

Do I need a specific folder structure to create daily work reports from my repository?▼

Creating daily work reports requires a specific folder structure storing progress data in docs/LOGS/ and docs/TODO.md. The Skill reads these paths and outputs the final generated report directly to docs/REPORTS/.

Why does my daily report not include recent git commits?▼

A daily report might miss recent git commits if the repository history is not updated or the specified YYYY-MM-DD parameter targets an incorrect date. Ensure the git log is accessible and the date parameter matches the intended workday.