author-contributions

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

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill author-contributions-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/author-contributions
Command: npx skills add https://github.com/Niiihuel/openide --skill author-contributions-niiihuel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When reviewing a branch before merge, it is hard to know exactly which files a specific person authored, especially when files were renamed or moved by other contributors. This Skill audits git history to attribute every file in the merge diff to a given author. ## Core Features & Use Cases - Author Attribution: Resolves the exact git identity of a contributor and collects every file they directly committed to on a branch versus its upstream. - Rename Tracing: Builds a rename map across all branch commits and walks it transitively, so contributions survive multi-hop file moves and bulk refactors. - Merge-Diff Filtering: Reports only files that will actually land in the upstream, excluding work that was later deleted, and returns a markdown table with DIRECT or VIA_RENAME status plus line stats. - Use Case: Before merging a long-lived feature branch, run this as a subagent to produce an authorship audit table showing exactly what a specific engineer contributed, including code that moved directories during refactors. ## Quick Start Ask the agent to find every file that a named author contributed to on the 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 that set against git diff upstream..branch so only files that will actually merge are reported.

How to track code contributions through file renames in git?▼

Extract rename entries from git diff-tree -r -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 see if any ancestor path was touched by the author.

Why does git author matching fail for some contributors?▼

The --author flag does substring matching, so short usernames may not match full display names or may match the wrong person. Resolve the exact identity first with git log --format="%an <%ae>" or the GitHub MCP get_me tool before filtering commits.

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

No. Only files present in the merge diff between the upstream and the branch are reported, since deleted files will not land in the upstream. Files the author touched but that were removed entirely are excluded from the final table.

Can this run as a subagent instead of inline?▼

Yes, and it is recommended. The procedure runs many sequential git commands, so delegating it to a subagent keeps the main context clean and returns only the concise markdown table with DIRECT or VIA_RENAME status and line statistics.