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, including contributions hidden behind rename chains. ## 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 attribution: Builds a transitive rename map across all branch commits so contributions survive multi-hop file moves (e.g., contrib/chat/ → agentSessions/ → sessions/). - Merge-scoped reporting: Only reports files present in the final upstream..branch diff, excluding files that were touched but later deleted. - Use Case: Before merging a long-lived feature branch, run this as a subagent to produce a markdown table classifying each file as DIRECT or VIA_RENAME with line stats, so reviewers know exactly what one author changed. ## Quick Start Ask the agent to find every file that a specific author contributed to on your current branch compared to main, tracing contributions through renames, and return a markdown table with status, file path, and line counts.
