author-contributions

Identify files an author contributed to on a branch, tracing contributions through git renames.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill author-contributions-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill author-contributions-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining exactly which files a specific person contributed to on a feature branch is hard with plain git commands, especially when files were renamed by other contributors. This Skill audits authorship across a branch versus its upstream and produces a concise table suitable for merge reviews. ## Core Features & Use Cases - Exact author resolution: Matches the requested person to their precise git identity using git log or the GitHub MCP get_me tool, avoiding false matches on similar names. - Rename-aware tracing: Builds a rename map from every commit on the branch and walks it transitively, so contributions survive multi-hop moves like contrib/chat/ → agentSessions/ → sessions/. - Merge-diff classification: Reports only files that will actually land in the upstream, labeling each as DIRECT or VIA_RENAME with +/- line stats. - Use Case: Before merging a long-lived branch, run this as a subagent to audit what a specific engineer authored and get a markdown table with a total line summary. ## Quick Start Ask the agent to find every file that a named author contributed to on your current branch compared to main, tracing renames, and return a markdown table with status, file path, and line changes.

Frequently Asked Questions about author-contributions

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

FAQPage Schema
How do I find all files an author changed on a git branch?▼

Use git log with --author to list the author's commits on the branch, then run git diff-tree on each commit to collect touched files. Cross-reference the results with git diff against the upstream so only files that will actually merge are reported.

How to track code contributions through git file renames?▼

Extract rename entries from git diff-tree -M output for every commit on the branch and build a map of new paths to old paths. Walk that map transitively from each file in the merge diff to check whether any ancestor path was touched by the author.

Why does git log --author match the wrong person?▼

The --author flag does substring matching, so short names can match multiple contributors. Resolve the exact identity first with git log --format="%an <%ae>" or the GitHub MCP get_me tool, then use the full display name.

Does this include files the author edited that were later deleted?▼

No. Only files present in the merge diff between the branch and upstream are reported, since deleted files will not land in the upstream. Files touched and later removed are excluded by design.

Should this analysis run as a subagent?▼

Yes. The procedure executes many sequential git commands, so delegating it to a subagent keeps the main context clean. The subagent returns a concise markdown table with status, file path, line changes, and a summary total.