author-contributions

Name: author-contributions
Availability: InStock
Author: aadorian

Trace author-contributed files across git branches with rename-aware history.

Updated Mar 28, 2026

Search Tags:#git #authorship #code-ownership #merge-review #branch-audit #rename-tracking

Ready to run

npx skills add https://github.com/aadorian/VSCode_Readme --skill author-contributions-aadorian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/collaboration-workflows/skill-author-contributions
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill author-contributions-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you audit authorship on a branch by identifying every file a specific author contributed to, even when the code moved through renames or refactors.

Core Features & Use Cases

Author matching: Resolves the exact git identity before searching commits, reducing false matches.
Rename-aware tracing: Follows file history through rename chains so moved code is still attributed correctly.
Merge-ready reporting: Produces a concise markdown table with status and line stats for review before merging.
Use case: Check which files a teammate changed on a feature branch, or verify how much of a refactor came from one author versus upstream.

Quick Start

Ask for every file a named author contributed to on a branch versus upstream, and return the results as a concise markdown table with rename-traced paths and line statistics.

Frequently Asked Questions about author-contributions

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

FAQPage Schema

How do I trace git author contributions across file renames on a branch?▼

To trace git author contributions across renames, resolve the exact author identity, search branch commits against an upstream reference, and follow transitive rename chains to attribute moved code correctly.

What is the best way to audit code ownership before merging a feature branch?▼

Auditing code ownership before a merge involves comparing branch history against upstream, matching exact git identities, and generating a concise markdown table with file paths, statuses, and line statistics.

Does git follow file history through multiple rename chains for authorship attribution?▼

Git history often loses attribution through refactors, but applying transitive rename tracing ensures that moved code is still correctly attributed to the original author on the branch.

How do I find every file a specific teammate changed on a branch versus upstream?▼

Finding every file a teammate changed requires matching their exact git author identity, filtering branch commits against the upstream reference, and tracing renames to capture all affected paths.

Can I generate a merge review report with line statistics for a single author's commits?▼

Generating a merge review report for a single author involves auditing their specific commits on the branch and outputting a concise markdown table with rename-traced paths, status, and line statistics.

Why does my git authorship audit miss files that were moved or refactored?▼

Git authorship audits miss moved files when rename chains are not traced transitively, causing the history to break; applying rename-aware tracing reconnects the moved code to the original author.