git-brag

List commits authored by the current git user that touch a specified path.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/guidodinello/claude-dotfiles --skill git-brag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-brag
Source: https://github.com/guidodinello/claude-dotfiles/tree/main/.claude/skills/git-brag
Command: npx skills add https://github.com/guidodinello/claude-dotfiles --skill git-brag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds all commits you authored that touched a given path, formatted for brag/perf-review documentation.

Core Features & Use Cases

  • Identify commits you authored that touched a specified path for performance reviews, brag docs, or contribution audits.
  • Expand each commit to show the changed files and present results in a clean, markdown-friendly format.
  • Use cases include documenting code contributions for a sprint or performance review.

Quick Start

Identify all commits authored by you that touched a specified path and present them in a clean markdown list suitable for a brag doc.

Frequently Asked Questions about git-brag

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

FAQPage Schema
How do I find git commits I authored for a performance review or brag doc?

Finding git commits for a brag doc involves filtering repository history by the current git user and a specified path. This identifies your contributions, returning matching commit hashes, author dates, and subjects formatted for markdown documentation.

How do I list my code contributions for a specific directory in git?

To list code contributions, apply a repository path or glob to git log filtered by your user.name and user.email. It returns matching commits and expands each one with git diff-tree to show changed files in a markdown-friendly list.

Can I generate a markdown list of my git commits for a specific project path?

Yes, you can generate a markdown list of git commits by querying history with your git user identity and target path. The results present commit hashes, author dates, and subjects suitable for markdown documentation and review.

What is the best way to audit my git contributions across a repository path?

The best way to audit git contributions is running git log with an author filter derived from your user.name and user.email against a specified path. This outputs a clean, markdown-friendly list of your commits for review.

Do I need any external dependencies to extract my git commits for a sprint review?

No external dependencies are required to extract git commits for a sprint review. The process solely uses standard git commands like git log and git diff-tree to find and expand commits authored by the current user touching a specified path.