skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

investigate-file-changes

Trace file changes and authors using git blame and log commands.

2|Updated Apr 11, 2026
Search Tags:#git#investigate#code-review#root-cause#commit-history#blame#file-changes
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill investigate-file-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate-file-changes
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/investigate-file-changes
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill investigate-file-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify who changed specific files and what changed, enabling correlation of regressions or breakages with commits and authors.

Core Features & Use Cases

  • Blame viewing: pinpoint the author and change details for a given line or range.
  • Commit history for a file: list commits that touched the file and inspect diffs.
  • Regression tracing: compare patches between commits to identify the source of regressions.
  • PR/root-cause summaries: generate concise summaries suitable for PR notes and incident reviews.

Quick Start

Ask the AI to identify who changed a given file and what changed, by querying git blame and git log, and present a concise summary.

Frequently Asked Questions about investigate-file-changes

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

FAQPage Schema
How do I find who changed a specific file in a git repository?▼

To find who changed a specific file in a git repository, use git blame and git log commands to correlate authors with changes. This identifies the authors and details of modifications to support regression tracing.

What is the best way to trace a regression using git commit history?▼

Tracing a regression using git commit history involves comparing patches between commits that touched a specific file. By inspecting diffs with git show, you can identify the source of the breakage.

Can I generate a root-cause summary for incident reviews from git blame?▼

Yes, you can generate a root-cause summary for incident reviews from git blame. The process outputs concise results correlating authors and changes, suitable for PR notes and incident analysis.

Does this git investigation approach modify my repository?▼

No, this git investigation approach does not modify your repository. It uses read-only git operations including log, blame, and show to pinpoint authors and inspect diffs without altering files.

How do I limit git blame output to specific file paths?▼

To limit git blame output to specific file paths, pass the file paths after a double dash. This restricts the commit history and blame results to only the targeted files.

Related Skills

Explore More Software Engineering Skills→
jcdendritejcdendrite
4

git-state-safety

Inspect other refs read-only during Git merge, rebase, or cherry-pick conflicts.

Community
Intermediate
carlkiblercarlkibler
3

post-mortem

Analyze failure incidents to identify root causes and generate lessons learned.

Community
Advanced
cwijayasundaracwijayasundara
3

harness-core

Automate build, test, deployment, and code review in CI/CD pipelines.

Community
Advanced
nimadorostkarnimadorostkar
25

git-workflow

Manage Git repository history through atomic commits, interactive rebasing, and automated bisection.

Community
Advanced