Overview

Git Search discovers git repositories under ~/Code and lists recent commits for each one. It helps you quickly gauge activity across multiple projects by showing the latest changes in a single view. It excludes .build checkouts to keep results focused.

How This Skill Works

A shell script scans ~/Code for repos, then runs git commands to fetch the last N commits for each repository. It prints a per-repo header followed by the commits, skipping any .build checkouts.

When to Use It

• When you want the last commits across all projects in ~/Code
• When you need a quick recent history for multiple repos
• During code reviews spanning several repositories in ~/Code
• To monitor activity across your codebase without opening every repo
• When preparing a summary of recent changes for teammates

Quick Start

1. Step 1: Open a terminal
2. Step 2: Run scripts/list_commits.sh --count 10
3. Step 3: Review the per-repo commit lists

Best Practices

• Use --count to limit output and keep results readable
• Ensure you're scanning the correct path ~/Code and that .build checkouts are excluded
• Run periodically to track activity trends
• Combine with grep or filtering to focus on specific authors or messages
• Verify results by inspecting the actual repos for deeper details

Example Use Cases

• scripts/list_commits.sh --count 10
• Run with --count 25 to surface more history
• View latest changes across all repos in ~/Code
• Exclude .build checkouts to avoid noise
• Output shows per-repo sections with commits

Frequently Asked Questions