Analyze git commit history within a time range to generate a 7-dimension retrospective report.
npx skills add https://github.com/gmh5225/k-skills --skill git-review-gmh5225
Please help me install this Agent Skill. Skill: git-review Source: https://github.com/gmh5225/k-skills/tree/main/skills/productivity/git-review Command: npx skills add https://github.com/gmh5225/k-skills --skill git-review-gmh5225
Manually reviewing git commit history to summarize work progress is time-consuming, error-prone, and difficult to standardize for regular retrospectives or team reporting. Developers and engineering managers often spend excessive time compiling work done over a day, week, or custom time range, and struggle to identify patterns, gaps, or improvement opportunities in their commit habits.
notes/daily_notes/ directory) to compare planned vs actual work, identifying uncompleted tasks or extra unplanned work.Use the git-review skill to analyze all commits from yesterday in the current git repository and generate a work retrospective report.
High-intent search queries and answers about installing and using this skill.
Generating a work retrospective from git commits involves analyzing the commit history within a specified time range to automate work summaries, track technical changes, and audit commit practices. This process eliminates manual review effort by producing a structured 7-dimension analysis report covering work rhythm and improvement suggestions.
Yes, analyzing git commits for a custom date range is supported using natural language time specifications like "last 3 days", "yesterday", or "this week". The tool automatically converts these inputs into valid git log parameters to filter the commit history for the retrospective report.
The git commit analysis evaluates commit practices and work rhythm by applying a 7-dimension structured analysis framework. It scores commit practices, identifies technical decisions, tracks change type distribution, and checks completion status to provide actionable improvement suggestions.
Yes, the retrospective report supports daily notes integration by cross-referencing personal notes stored in the standard `notes/daily_notes/` directory. This feature compares planned tasks against actual git commits to identify uncompleted tasks or extra unplanned work.
The git work summary report produces a styled HTML output for easy viewing and optionally converts it to PDF format. This multi-format output allows for straightforward local review and sharing via collaboration tools like Feishu.
Standardizing weekly work progress reporting is best achieved by automating the extraction of commit history into a structured 7-dimension analysis report. This approach tracks team progress, audits commit quality, and generates consistent technical change summaries without manual compilation effort.
kamalsroor1Initialize a Git repository with an initial commit when none exists.
tassiovaleCreate HTML/CSS research posters with AI-generated visuals and export to PDF or PowerPoint.
miko06Automate interactive review, benchmarking, and scoring of developer experience plans.
algorithmbasicsAnalyze commit history and code quality metrics to produce weekly engineering retrospective reports.