author-contributions

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill author-contributions-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill author-contributions-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining exactly which files a specific person contributed to on a feature branch is hard with plain git commands, especially when files were renamed or moved by other contributors during the branch's lifetime. This skill produces a clear audit table of an author's contributions relative to an upstream branch. ## 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 tracing: Builds a rename map across all branch commits and walks it transitively, so contributions survive multi-hop moves like contrib/chat/ → agentSessions/ → sessions/. - Merge-diff classification: Reports only files that will actually land in the merge, labeling each as DIRECT or VIA_RENAME with line-change stats. - Use Case: Before merging a long-lived branch, a reviewer asks which files a specific engineer touched; the skill returns a markdown table with status, file path, and +/- line counts plus a summary total. ## Quick Start Ask the agent to find every file that a named author contributed to on your current branch compared to main, tracing contributions through renames, and return the results as a markdown table.

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 the results with git diff --name-only against the upstream to keep only files that will actually merge.

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

Extract rename records from every branch commit using git diff-tree -r -M 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 target author.

Why does git author search match the wrong person?▼

The --author flag does substring matching, so short names can match multiple contributors with similar display names. 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 final merge diff between the upstream and the branch are reported. Files the author touched that were subsequently deleted entirely are excluded because they will not land in the upstream.

Can this run as a subagent instead of inline?▼

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