You can trace any piece of code back to the agent session that created it. The commit-context skill uses git blame and a memory lookup to find the commit and the linked session. It answers questions like why a certain line exists or what the agent was doing when that code changed.
When you point to a file, function, or line number, the skill first finds the commit SHA using git commands. Then it looks up that commit in your agent's memory. The result shows the commit details and any linked agent session with observations.
If no session exists for a commit, the skill reports this honestly. It never invents intent or makes up information. This helps you understand the true history behind your codebase.
Global
mkdir -p ~/.claude/skills/commit-contextProject
mkdir -p .claude/skills/commit-contextSource Repository
Caveman Commitjuliusbrussee/caveman
Generate ultra-compressed commit messages with Conventional Commits format
Verification Before Completionobra/superpowers
Always run fresh verification before claiming work is complete or passing
Using Git Worktreesobra/superpowers
Isolate your feature work with git worktrees and keep your main branch safe
Finishing A Development Branchobra/superpowers
Finish your development branch with merge, pull request, or cleanup options
Git Guardrails Claude Codemattpocock/skills
Stop dangerous git commands from running automatically with safety hooks
Setup Pre Commitmattpocock/skills
Automate code formatting type checking and tests before every commit
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes
Git Advanced Workflowswshobson/agents
Master advanced Git workflows for clean history and confident recovery