git-activity

Scan git repositories and group recent commits by repository.

4|Updated Jan 16, 2019
One-click install
npx skills add https://github.com/four43/dotfiles --skill git-activity-four43
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-activity
Source: https://github.com/four43/dotfiles/tree/main/claude/skills/git-activity
Command: npx skills add https://github.com/four43/dotfiles --skill git-activity-four43

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan your git history across multiple repositories to produce a concise activity summary for standups and progress checks.

Core Features & Use Cases

  • Scan all git repositories under a directory for commits by the current user in a lookback window.
  • Group results by repository and present a clear summary suitable for standups and Jira comparisons.
  • Optionally fetch remotes to include remote-only commits before summarizing.

Quick Start

Run git-activity ~/projects to generate a per-repo activity summary of your recent commits.

Frequently Asked Questions about git-activity

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

FAQPage Schema
How do I summarize recent git commits across multiple repositories for a standup?

To summarize recent git commits across multiple repositories for a standup, you can scan a parent directory containing your repos. The tool groups your recent commits by repository and presents a clear summary suitable for progress checks.

Can I filter git activity by a specific author when scanning local repositories?

Yes, you can filter git activity by a specific author when scanning local repositories. The tool supports an author filter to ensure the summary only includes commits made by the specified user across your configured lookback window.

Does the tool support fetching remote-only commits before summarizing git history?

Yes, the tool supports fetching remote-only commits before summarizing git history. It can optionally fetch remotes to include remote-only commits before grouping and presenting the activity summary.

What is the best way to cross-reference git commits with Jira for progress updates?

The best way to cross-reference git commits with Jira for progress updates is to generate a per-repo activity summary of your recent commits. You can then compare this grouped commit history against your Jira tickets for accurate progress tracking.

Can I scan all local and remote branches to track personal coding activity?

Yes, you can scan all local and remote branches to track personal coding activity. The tool scans all available branches within your repositories to ensure comprehensive commit tracking for your activity summary.