war-report

Generate weekly activity reports from git commits across repositories.

Updated Apr 11, 2023
One-click install
npx skills add https://github.com/salverius-tech/dotfiles --skill war-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: war-report
Source: https://github.com/salverius-tech/dotfiles/tree/main/home/dot_claude/skills/war-report
Command: npx skills add https://github.com/salverius-tech/dotfiles --skill war-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of weekly activity reports from git commit history, saving developers time and ensuring consistent documentation of accomplishments.

Core Features & Use Cases

  • Automated Commit Analysis: Scans specified directories for git repositories and gathers commits within a defined weekly range (Sunday-Saturday).
  • Prior Report Review: Analyzes previous reports to identify and integrate ongoing work threads.
  • Concise Summarization: Synthesizes commit data into clear, bulleted accomplishment summaries.
  • Use Case: At the end of each week, activate this Skill to automatically compile a report of all code committed across your work projects, highlighting key achievements and progress on ongoing tasks.

Quick Start

Generate my war report for the past week.

Frequently Asked Questions about war-report

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

FAQPage Schema
How do I generate a weekly activity report from git commits?

To generate a weekly activity report from git commits, you can automatically scan specified directories for repositories, gather commits within a Sunday-Saturday timeframe, and synthesize the logs into bulleted accomplishment summaries.

Can I track ongoing work threads across multiple git repositories?

You can track ongoing work threads across multiple git repositories by analyzing previous weekly activity reports to identify and integrate prior tasks into the current commit log summaries.

What's the best way to automate developer productivity reporting?

Automating developer productivity reporting is best achieved by scanning local git repositories for commits within a defined weekly range and synthesizing the data into concise, bulleted documentation of accomplishments.

Does generating a git activity log require manual date range configuration?

Generating a git activity log does not require manual date range configuration, as the process automatically operates within a defined Sunday-Saturday weekly timeframe to gather commits.

How are commit logs summarized in the weekly activity report?

Commit logs are summarized in the weekly activity report by synthesizing raw git commit data into clear, bulleted accomplishment summaries to ensure professional and accurate documentation of developer work.

Where are the generated weekly git reports stored?

The generated weekly git reports are stored in a designated directory, ensuring consistent documentation and allowing subsequent reports to review prior ongoing work threads.