author-contributions

Trace author file contributions through renames using git commands.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill author-contributions-devflex-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-contributions
Source: https://github.com/DevFlex-AI/devonz-editor-web/tree/main/.github/skills/author-contributions
Command: npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill author-contributions-devflex-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify all files contributed by a specific author on a branch relative to upstream, tracing contributions through renames.

Core Features & Use Cases

  • Rename-aware attribution: traces edits across file renames to preserve accurate authorship.
  • Branch-level auditing: quickly generate a concise table showing direct contributions (DIRECT) and those via renames (VIA_RENAME).
  • Use Case: before merging a feature branch, audit who touched which files and verify attribution.

Quick Start

Provide the author's exact name and the branch to compare against the upstream to generate a concise attribution table.

Frequently Asked Questions about author-contributions

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

FAQPage Schema
How do I audit an author's contributions across git branches before a merge?▼

To audit git author contributions before merges, this skill executes multiple git commands like log and diff to classify files contributed by a specific author on a branch relative to upstream, producing a concise attribution table.

Can I trace file renames to accurately attribute git contributions to an author?▼

Yes, rename-aware attribution traces edits across file renames by executing git diff-tree commands, preserving accurate authorship by classifying contributions as either DIRECT or VIA_RENAME in the output table.

What is the best way to review cross-branch contributions by a specific developer?▼

Reviewing cross-branch contributions requires providing the author's exact name and the target branch to compare against upstream, generating a concise table that maps direct file edits and contributions traced through renames.

Does this git attribution tool require any external dependencies or plugins?▼

No external dependencies are required, as the skill operates as standalone scripts utilizing standard git commands to identify contributed files and trace authorship through renames on a given branch.

How do I prepare merge decisions based on who touched which files on a feature branch?▼

To prepare merge decisions, the skill audits who touched which files on a feature branch relative to upstream, outputting a table that distinguishes direct file contributions from those tracked via rename.

When should I use rename-aware attribution for git branch auditing?▼

Use rename-aware attribution when auditing authorship before merges where files may have been renamed, ensuring accurate cross-branch contribution tracking by tracing edits rather than just matching file paths.