← ClaudeAtlas

author-contributionslisted

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
Pointa-Labs/basehalf · ★ 15 · API & Backend · score 73
Install: claude install-skill Pointa-Labs/basehalf
When asked to find all files a specific author contributed to on a branch (compared to main or another upstream), follow this procedure. The goal is to produce a simple table that both humans and LLMs can consume. ## Run as a Subagent This skill involves many sequential git commands. Delegate it to a subagent with a prompt like: > Find every file that author "Full Name" contributed to on branch `<branch>` compared to `<upstream>`. Trace contributions through file renames. Return a markdown table with columns: Status (DIRECT or VIA_RENAME), File Path, and Lines (+/-). Include a summary line at the end. ## Procedure ### 1. Identify the author's exact git identity ```bash git log --format="%an <%ae>" <upstream>..<branch> | sort -u ``` Match the requested person to their exact `--author=` string. Do not guess — short usernames won't match full display names (resolve via `git log` or the GitHub MCP `get_me` tool). ### 2. Collect all files the author directly committed to ```bash git log --author="<Exact Name>" --format="%H" <upstream>..<branch> ``` For each commit hash, extract touched files: ```bash git diff-tree --no-commit-id --name-only -r <hash> ``` Union all results into a set (`author_files`). ### 3. Build rename map across the entire branch For **every** commit on the branch (not just the author's), extract renames: ```bash git diff-tree --no-commit-id -r -M <hash> ``` Parse lines with `R` status to build a map: `new_path → {old_paths}`. ### 4. Get the mer