work-report

Generate Git commit-based work reports from directory file paths and README files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/octkp/base --skill work-report-octkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-report
Source: https://github.com/octkp/base/tree/main/dotfiles/claude/skills/work-report
Command: npx skills add https://github.com/octkp/base --skill work-report-octkp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of work reports by analyzing Git commit history within a specific directory, saving developers time and effort in manually compiling their progress.

Core Features & Use Cases

  • Automated Report Generation: Creates detailed work reports based on Git commit history and file path analysis.
  • Period Specification: Supports various timeframes like "yesterday," "this week," "last month," or custom date ranges.
  • Categorization: Organizes work into categories such as 'Investigation', 'Implementation', 'Study Session', and 'Other' based on directory structure.
  • Use Case: A developer can request "Generate my report for last week," and the Skill will produce a Markdown document detailing all commits made in the docs/takano directory, summarizing the work done.

Quick Start

Use the work-report skill to generate a report for last week's commits in the docs/takano directory.

Frequently Asked Questions about work-report

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

FAQPage Schema
How do I automate work report generation from Git commit history?

Automating work report generation from Git commit history requires parsing file paths within a specified directory and extracting information from associated README files. This Skill compiles commit logs and document content into a categorized Markdown report.

How does generating a work report from a Git directory structure work?

Generating a work report from a Git directory works by parsing file paths and extracting associated README file content. The mechanism categorizes commit logs into investigation, implementation, study sessions, and others based on the directory structure.

Can I generate a Git commit report for a specific timeframe like last week?

You can generate a Git commit report for specific timeframes including yesterday, this week, last month, or custom date ranges. The Skill processes commit logs within the specified period to compile the final report.

Do I need Git command-line tools to generate commit-based work reports?

You need Git command-line tools and file system access to generate commit-based work reports. These dependencies are required to parse commit logs, read directory paths, and extract README file content for report compilation.

What is the best way to categorize Git commits into investigation and implementation tasks?

The best way to categorize Git commits into investigation and implementation tasks is by analyzing the directory structure. This Skill automatically organizes commit history into categories like Investigation, Implementation, and Study Session based on file paths.

What are the limitations of using directory structure for commit report categorization?

A limitation of using directory structure for commit report categorization is that work must be organized into specific folders to be classified correctly. Commits outside the targeted directory paths or lacking associated README files may not be fully captured.