skills.rest
darwinboaventura
darwinboaventuraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

author-contributions

Trace an author's file contributions through renames on a branch.

Updated Feb 18, 2026
Search Tags:#git#audit#rename#branch#contributions#author
One-click install
npx skills add https://github.com/darwinboaventura/base-vscode-copilot --skill author-contributions-darwinboaventura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/darwinboaventura/base-vscode-copilot/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/darwinboaventura/base-vscode-copilot --skill author-contributions-darwinboaventura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify all files a specific author contributed to on a branch by tracing contributions through file renames and presenting a concise table of impact.

Core Features & Use Cases

  • Resolve an author's exact git identity on a branch using git log.
  • Collect all files touched by the author on the branch, across all commits.
  • Build a rename map across the full history to follow moves and renames.
  • Classify files in the branch diff as DIRECT (authored) or VIA_RENAME (through renames), and provide a summary of changes.
  • Use cases include auditing edits before merges, understanding code ownership, and verifying accountability for branches.

Quick Start

Provide the author name and branch to analyze; the tool will output a table showing DIRECT and VIA_RENAME contributions for that author.

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 a git branch that includes renames?▼

Trace an author's git contributions across a branch by building a rename map from commit history, then classifying files as DIRECT or VIA_RENAME to audit authorship before merges. This provides a merge-ready diff summary of their impact.

What's the best way to audit git authorship before merging a refactor branch?▼

Audit git authorship before merging by comparing the branch against upstream and collecting all files touched by the specific author. The tool resolves exact identity through git log and tracks renames to ensure full accountability for refactored code.

Can I identify all files a specific developer modified on a branch if files were moved?▼

Identify all files a developer modified on a branch even after moves by tracing contributions through file renames. The tool builds a historical rename map to classify each file in the branch diff as authored directly or reached via rename.

How does rename tracking work when auditing git contributions on a branch?▼

Rename tracking for git contribution audits works by mapping file moves across the full branch history. It classifies branch diff files as DIRECT if the author edited them, or VIA_RENAME if the author's contributions reached them through file renames.

Do I need to compare a branch against main to resolve an author's exact git identity?▼

Comparing a branch against upstream like main is required to resolve an author's exact git identity and audit their contributions. This comparison isolates branch-specific commits to list per-commit files and generate a merge-ready impact summary.

Related Skills

Explore More Software Engineering Skills→
sluongngsluongng
6

buck2-stack-maintainer

Rebase fork/stack onto origin/main and publish merge commits to fork/main.

Community
Advanced
DevFlex-AIDevFlex-AI

author-contributions

Trace author file contributions through renames using git commands.

Community
Advanced
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
dudeofawesomedudeofawesome
4

notify-blame

Identify Git blame authors and notify them on Slack with MR links.

Community
Intermediate