bms:git-log-summary

Summarize git log changes grouped by feature or area with commit IDs and authors.

68|14|Updated Dec 21, 2017
One-click install
npx skills add https://github.com/benmatselby/dotfiles --skill bms-git-log-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bms:git-log-summary
Source: https://github.com/benmatselby/dotfiles/tree/main/agents/skills/git-log
Command: npx skills add https://github.com/benmatselby/dotfiles --skill bms-git-log-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, automatic summary of git history for a defined time window, helping teams quickly understand changes without parsing individual commits.

Core Features & Use Cases

  • Group changes by feature or area to reveal scope and impact
  • Include commit IDs and authors adjacent to each entry for traceability
  • Support for a time window or range to tailor summaries for releases or sprints

Quick Start

Ask this skill to summarize the latest commits for the current repository.

Frequently Asked Questions about bms:git-log-summary

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

FAQPage Schema
How do I summarize git log history for a specific time window?

To summarize git log history, you can generate a concise overview of changes within a defined period. This process groups commits by feature or area, includes commit IDs and authors for traceability, and analyzes diffs for accurate release planning.

What is the best way to group git commits by feature for a sprint review?

Grouping git commits by feature reveals the scope and impact of changes for a sprint review. It analyzes actual code diffs rather than relying only on commit titles, providing a concise summary of development progress.

Can I generate a release overview from a git diff instead of just commit titles?

Yes, generating a release overview from a git diff provides a deeper understanding of changes. It analyzes the actual diffs alongside commit titles to automatically summarize git history for any repository size.

Does git log feature grouping work for large repositories?

Git log feature grouping is applicable to any repository size. It helps teams quickly understand changes without parsing individual commits, making it suitable for large-scale release planning and code reviews.

How do I include commit IDs and authors in an automated git log summary?

To include commit IDs and authors in an automated git log summary, the tool appends this traceability data in brackets adjacent to each entry. This ensures clear attribution during code reviews.