PR Attribution

Analyze branch commits and line changes to report PR attribution.

Updated Aug 23, 2026

Search Tags:#git #pr #pull-request #commit-history #blame #authorship #branch-analysis

Ready to run

npx skills add https://github.com/zmchenry/dotfiles --skill pr-attribution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: PR Attribution
Source: https://github.com/zmchenry/dotfiles/tree/main/.claude/skills/pr-attribution
Command: npx skills add https://github.com/zmchenry/dotfiles --skill pr-attribution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you understand exactly who will be credited for changes when you create a PR by analyzing commits, authorship, and line-by-line changes on your feature branch.

Core Features & Use Cases

Commit attribution: Lists commits on the branch with author information and relative times.
Line-level attribution: Shows who last modified each changed line in modified files.
PR readiness: Provides a clear summary for reviewers about who contributed what.

Quick Start

Run the tool on your current branch to preview attribution before creating a PR.

Frequently Asked Questions about PR Attribution

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

FAQPage Schema

How do I check who will be credited for commits in a pull request?▼

Pull request attribution identifies contributing authors by analyzing your feature branch's commit history and line-by-line changes. This reveals exactly who will be credited before you create the PR.

Can I see line-level authorship for modified files in a git branch?▼

Yes, line-level authorship uses git blame to show who last modified each changed line in your modified files. This provides a detailed breakdown of individual line contributions within the branch.

Does git blame attribution work correctly after rebasing or merging a feature branch?▼

Git blame attribution works with typical Git workflows including rebasing and merging. It relies on local Git metadata from branch logs and blame data to accurately trace authorship through these common operations.

Do I need external dependencies or tools to analyze PR commit history?▼

No external dependencies are needed to analyze PR commit history. The tool relies entirely on local Git metadata such as branch data, logs, and blame information to output a structured attribution report.

What is the best way to generate a PR readiness summary for reviewers?▼

Generate a PR readiness summary by analyzing your current branch's commits and line-level changes. This produces a structured attribution report detailing exactly who contributed what for your reviewers.