git-commits

Search and create git commits across local repositories using git log conventions.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill git-commits-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/arayaroma/ether/tree/main/skills/git-commits
Command: npx skills add https://github.com/arayaroma/ether --skill git-commits-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives you a consistent way to look up commit history across one or many local repositories and to create new commits that follow your existing conventions, without building any separate tracking database. ## Core Features & Use Cases - Commit history search: Query commits by hash, date, title, and body using git log with --since, --grep, and --author filters, across a single repo or all repos under a workspace directory. - Convention-following commits: Inspects recent history with git log -5 to match the repo's existing commit style, stages explicit files only, and verifies with git status and git diff --staged before committing. - Use Case: Ask "what did I commit this week across my projects" and get a parsed list of hash, date, title, and description per repo, or ask for a commit of staged changes written in your repo's style. ## Quick Start Ask the assistant to show what commits you made this week across all repos in your workspace.

Frequently Asked Questions about git-commits

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

FAQPage Schema
How do I search git commit history across multiple repositories?▼

Run git log with a custom format like --pretty=format:'%H|%ad|%s|%b' in each repo under your workspace directory, then parse the output into hash, date, title, and body. Filter server-side with --since, --grep, or --author instead of pulling full history.

How to find commits by date or keyword in git?▼

Use git log with --since for date ranges (e.g. --since='1 week ago') and --grep for keyword matching in commit messages. Adding --author narrows results to a specific contributor, keeping queries fast without client-side filtering.

Does this skill push commits to a remote repository?▼

No, pushing is explicitly out of scope. The skill only tracks history and creates local commits; a push happens only if the user separately asks for it.

Why does the skill avoid git add -A when committing?▼

Staging explicit files prevents accidentally committing unrelated or sensitive changes. The skill runs git status and git diff --staged first so you can confirm exactly what will go into the commit.

When should I not use git log for commit tracking?▼

Avoid building a separate database to mirror commit history, since git already indexes everything git log needs. A duplicate catalog would just become a stale copy requiring constant synchronization.