fix-author

Rewrite commit authors in main..HEAD to match local or global git config.

2|Updated Jul 5, 2018
One-click install
npx skills add https://github.com/tnez/dotfiles --skill fix-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-author
Source: https://github.com/tnez/dotfiles/tree/main/claude/dot-claude/skills/fix-author
Command: npx skills add https://github.com/tnez/dotfiles --skill fix-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many repositories accumulate commits with authors that do not reflect the local or global git config, causing attribution drift and inconsistent history.

Core Features & Use Cases

  • Identify mismatched commit authors by comparing each commit's author against the configured user.name and user.email (local override global).
  • List commits in the range main..HEAD and report which commits require correction.
  • Rewrite author information for affected commits using a safe rebase workflow and provide a summary of changes.

Quick Start

Run the fix-author script on your branch to rewrite commits between main and HEAD using your configured author.

Frequently Asked Questions about fix-author

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

FAQPage Schema
How do I fix commit authors to match my git config?

To fix commit authors, the Skill reads your local or global git config for user.name and user.email, lists commits in the main..HEAD range, and performs a rebase to amend author data. It provides a summary of the corrected commits.

How do I rewrite git history to correct author information on a feature branch?

Rewriting git history for author correction involves checking commits between main and HEAD. The Skill identifies mismatches against your configured user details and uses a rebase workflow to safely amend the author information on affected commits.

Does this author fix workflow use local or global git config?

The workflow uses both, but local git config takes precedence over global. It reads user.name and user.email from your git configuration to determine the correct author data for rewriting mismatched commits in your branch history.

What is the best way to resolve attribution drift in git history?

Attribution drift from inconsistent commit authors is resolved by comparing commits against your git config. This process lists commits requiring correction in the main..HEAD range and rewrites the author information using a safe rebase workflow.

Can I use this to fix author data during an interactive rebase?

Yes, the process is designed for feature branches and rebases. It identifies commits in the main..HEAD range where the author does not match your configured git user.name and user.email, then amends the authors during the rebase.