author-contributions

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

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/voidful/Aixlarity --skill author-contributions-voidful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/.github/skills/author-contributions
Command: npx skills add https://github.com/voidful/Aixlarity --skill author-contributions-voidful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When reviewing a branch before merge, it is hard to know exactly which files a specific author touched, especially when files were renamed by other contributors. This Skill audits authorship by comparing a branch against its upstream and producing a clear table of each author's contributions. ## Core Features & Use Cases - Exact Author Matching: Resolves the author's exact git identity from commit history before searching, avoiding false matches on similar names. - Rename Tracing: Builds a rename map across all branch commits and walks it transitively, so contributions survive multi-hop file moves. - Merge-Diff Classification: Labels each file as DIRECT or VIA_RENAME and reports line stats, covering only files that will actually land in the merge. - Use Case: Before merging a long-lived feature branch, run this to audit what a specific contributor changed and generate a review-ready markdown table with per-file +/- stats. ## 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?

Run git log with --author filtered to the exact author name over the upstream..branch range, then use git diff-tree on each commit to collect touched files. Cross-reference with git diff --name-only against the upstream to keep only files that will land in the merge.

How to track code contributions through file renames in git?

Build a rename map by running git diff-tree -r -M on every branch commit and parsing R-status lines into new-path to old-path mappings. Walk the map transitively from each merge-diff file to check whether any ancestor path was touched by the author.

Why does git author search 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>" and use the full display name to avoid mismatches like matching Joshua Smith when searching for Josh S.

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

No. Only files present in the merge diff between upstream and 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 in the main session?

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