Blame Why — Git skill for Claude Code
Explain why a specific line of code exists — git blame + commit context.
How to install Blame Why
Installs to ~/.claude/commands/utsabpanta-claude-code-toolkit-blame-why.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/utsabpanta/claude-code-toolkit/HEAD/.claude/commands/blame-why.md -o ~/.claude/commands/utsabpanta-claude-code-toolkit-blame-why.md Restart Claude Code, or start a new session, for it to be picked up.
What Blame Why does
description: Explain why a specific line of code exists — git blame + commit context argument-hint: : (e.g. src/auth.ts:42)
Explain why the code at $ARGUMENTS exists.
Steps:
- Parse the argument as
:. If it's not in that form, ask the user for a file and line. - Run
git blame -L ,to find the commit that last touched that line. - Run
git showto get the commit message and the surrounding change. - Read the code around the line
Alternatives in Git
- Fullstack Dev Skills — by jeffallan - A comprehensive Claude Code plugin with 65 specialized skills covering full-stack development a 7k ★
- 40+ Claude Code Tips — Tips for getting the most out of Claude Code, including a custom status line script, cutting the system prompt 5.8k ★
- Merge Command — Finalize worktree work: update docs, commit, merge to main, clean up 1.3k ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Glint
A liquid-glass status line for the Claude Code CLI: glass-gradient pill, context tracking, effort colors, git-
Claude Code Statusline Ps
PowerShell 7 status line for Claude Code on Windows: context meter, cost, rate limits, git branch, mode badges
Explain Issue Fix
by hackdays-io - Documents solution approaches for GitHub issues, explaining technical decisions, detailing ch
/commit
by evmts - Creates git commits using conventional commit format with appropriate emojis, following project sta
GitCommit
You are a commit message generator. Read the provided git diff and write a concise imperative commit message.
Commit Message Writer
Writes a Conventional Commits message from a git diff — tight subject line plus a why-focused body.
Related Agents
Reviso Finder History
Reviso finder — reads git blame and history of the modified code to find bugs in light of historical context.
Review History
Check git blame and historical context of modified code
Doc Drift Auditor
Verify documentation accuracy against implementation using git forensics and code analysis with file paths, li