author-contributions

Identify author-contributed files on a branch versus upstream, tracing renames.

Updated Mar 18, 2026

Search Tags:#git #audit #rename #branch #contributions #author

Ready to run

npx skills add https://github.com/colajacquin-e/ephcode --skill author-contributions-colajacquin-e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/colajacquin-e/ephcode/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/colajacquin-e/ephcode --skill author-contributions-colajacquin-e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames.

Core Features & Use Cases

Auditing authorship before merges by tracing file history across branches and renames.
Generating a concise table of contributions for stakeholders.
Verifying exact files touched by a given author on a feature branch.

Quick Start

Ask the AI to identify all files contributed by a specific author on a branch by comparing to upstream and tracing renames.

Frequently Asked Questions about author-contributions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace an author's file contributions across git branches?▼

Tracing an author's file contributions across git branches involves auditing commit history by comparing a feature branch against its upstream. This process identifies all specific files touched by an author and traces code lineage directly through file renames using git log sequences.

What is the best way to audit code ownership before a merge?▼

Auditing code ownership before a merge requires comparing the feature branch against its upstream and filtering commit logs by author. This generates a concise table classifying each modified file as either a direct contribution or a contribution via rename.

Can I verify which exact files a specific author touched on a feature branch?▼

Yes, you can verify the exact files a specific author touched on a feature branch by running a sequence of git diff and diff-tree commands against upstream. This audit produces a detailed summary table classifying all direct and renamed file contributions.

How does git track file contributions through renames?▼

Git tracks file contributions through renames by executing diff commands that detect renamed files and trace their historical commit logs. This mechanism classifies contributed files as VIA_RENAME instead of DIRECT, ensuring accurate authorship auditing across branches.

Does git log show files contributed by an author when compared to upstream?▼

Git log alone does not comprehensively show files contributed by an author compared to upstream. It must be combined with git diff-tree and git diff --stat commands to classify file contributions and trace them through branch renames effectively.

What are the limitations of auditing authorship across git branches?▼

Limitations of auditing authorship across git branches include potential inaccuracies if file renames are not detected by git diff commands. The audit relies strictly on comparing the branch to its upstream, meaning uncommitted local changes fall outside this scope.