Skill detail
author-contributions
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…
Why we recommend it: Git-based authorship tracing for VS Code branches, on the Git facet of VS Code workflow.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: author-contributions
description: 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.
---
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 merge diff file list
```bash
git diff --name-only <upstream>..<branch>
```
These are the files that will actually land when the branch merges.
### 5. Classify each file in the merge diff
For each file in step 4:
- If it's in `author_files` → **DIRECT**
- Else, walk the rename map transitively (follow chains: current → old → older) and check if any ancestor is in `author_files` → **VIA_RENAME**
- Otherwise → not this author's contribution
### 6. Get diff stats
```bash
git diff --stat <upstream>..<branch> -- <file1> <file2> ...
```
### 7. Return the table
Format the result as a markdown table:
```
| Status | File | +/- |
|--------|------|-----|
| DIRECT | src/vs/foo/bar.ts | +120/-5 |
| VIA_RENAME | src/vs/baz/qux.ts | +300 |
| ... | ... | ... |
**Total: N files, +X/-Y lines**
```
## Important Notes
- **Use Python for the heavy lifting.** Shell loops with inline comments break in zsh. Write a temp `.py` script, run it, then delete it.
- **Author matching is exact.** Always run step 1 first. `--author` does substring matching but you must verify the right person is matched (e.g., don't match "Joshua Smith" when looking for "Josh S."). Use the GitHub MCP `get_me` tool or `git log` output to resolve the correct full name.
- **Renames can be multi-hop.** A file may have moved `contrib/chat/` → `agentSessions/` → `sessions/`. The rename map must be walked transitively.
- **Only report files in the merge diff** (step 4). Files the author touched that were later deleted entirely should not appear — they won't land in the upstream.
- **The rename map must include all authors' commits**, not just the target author's. Other people often do the rename commits (e.g., bulk refactors/moves).
## Example Python Script
```python
import subprocess, os
os.chdir('<repo_root>')
UPSTREAM = 'main'
AUTHOR = '<Author Name>' # Resolve via `git log` or GitHub MCP `get_me`
# Step 2: author's files
commits = subprocess.check_output(
['git', 'log', f'--author={AUTHOR}', '--format=%H', f'{UPSTREAM}..HEAD'],
text=True).strip().split('\n')
author_files = set()
for h in (c for c in commits if c):
files = suRead the full source on GitHub (opens external page)