author-contributions

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

189k|41.5k|Updated Sep 3, 2015
One-click install
npx skills add https://github.com/microsoft/vscode --skill author-contributions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/microsoft/vscode/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/microsoft/vscode --skill author-contributions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill precisely identifies which files an author contributed to on a specific branch, even when those files have been renamed, providing clarity before merges and for code audits.

Core Features & Use Cases

  • Author Attribution: Accurately lists files directly committed by an author or modified via file renames.
  • Pre-Merge Auditing: Helps verify authorship and understand code ownership before integrating branches.
  • Use Case: Before merging a feature branch, use this Skill to confirm that all code attributed to a specific developer is correctly identified, even if refactoring occurred.

Quick Start

Find every file that author "Jane Doe" contributed to on branch feature/new-ui compared to main, tracing contributions through file renames.

Frequently Asked Questions about author-contributions

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

FAQPage Schema
How do I track code authorship through file renames on a git branch?

Tracking code authorship through file renames requires transitive rename map traversal to identify all files an author contributed to on a branch compared to its upstream. This ensures accurate attribution even after refactoring.

How does git contribution tracking handle files that have been renamed?

Git contribution tracking handles renamed files by traversing a transitive rename map, linking the current file path back to its original commits. This preserves accurate author attribution across refactoring boundaries.

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

Auditing code ownership before a merge involves comparing the feature branch against its upstream to list files modified by specific authors. This verifies authorship and clarifies contributions before integration.

Does git author attribution require exact author name matching?

Yes, git author attribution requires exact author matching to accurately identify contributions. The system compares the specified author string directly against commit metadata to filter and trace file modifications.

Can I identify all files a specific developer modified on a branch compared to main?

Yes, you can identify all files a developer modified on a branch compared to main by analyzing commits against the upstream base. The process traces contributions through any file renames to ensure complete attribution.

Why does my code audit miss author contributions when files are moved?

Your code audit misses author contributions when files are moved because standard logs often break at rename boundaries. Traversing a transitive rename map resolves this by linking the new file paths back to their original author history.