author-contributions

Identify files an author contributed to on a branch with rename tracing.

Updated Aug 23, 2026

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

Ready to run

npx skills add https://github.com/THRISHAL12345/Project_X --skill author-contributions-thrishal12345

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/author-contributions
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill author-contributions-thrishal12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify exactly which files a specific author contributed to on a branch compared with an upstream reference, even when files have been renamed.

Core Features & Use Cases

Authorship Audit: Quickly answer who changed what before a merge or review.
Rename-Aware Tracking: Follow contribution history through file moves and renames so credit is not lost.
Concise Reporting: Produce a human-readable markdown table with contribution status and line stats for fast review.
Use Case: Use it when you need to validate a contributor's scope of work on a feature branch before approving or merging it.

Quick Start

Ask for a rename-aware authorship report for the specified author on your branch compared with the chosen upstream and return a markdown table with contribution status and line counts.

Frequently Asked Questions about author-contributions

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

FAQPage Schema

How do I track an author's git contributions on a branch when files have been renamed?▼

To track an author's git contributions through file renames on a branch, you need rename-aware branch diff filtering against an upstream reference. This process traces contribution history across file moves so attribution is not lost during merge audits.

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

The best way to audit code ownership before a merge is to generate a concise contribution table that maps exact git authors to their modified files. This requires branch-wide rename tracing and merge-diff filtering to accurately validate a contributor's scope of work.

Can I generate a markdown table of specific author line stats compared to an upstream branch?▼

Yes, you can generate a human-readable markdown table of author line stats by applying exact git author matching and merge-diff filtering against an upstream branch. The report includes contribution status and line counts for fast review.

How does rename tracking work for git authorship attribution across a feature branch?▼

Rename tracking for git authorship attribution works by following a file's contribution history through moves and renames across a branch. This ensures credit is not lost when comparing an author's work relative to an upstream reference.

Why does my git author attribution miss files that were moved or renamed on the branch?▼

Git author attribution misses renamed or moved files because standard branch diffs do not track history across file paths. You need branch-wide rename tracing to connect the original file to its new path and preserve accurate contribution attribution.