git-context

# Git Context ## When to Use Use this skill when: - Understanding why code was written a certain way - Finding related changes across the codebase - Tracing the evolution of a feature or pattern - Identifying who has expertise in a module - Finding past bug fixes or regressions in an area ## What It Does Searches git history to build context about the codebase, using a combination of native git commands and the `sem` MCP tool for deeper analysis. Helps answer "why was this done this way?" and "what changed recently in this area?" ## How to Execute ### Find Recent Changes to a Module ```bash # Recent commits touching this area git log --oneline --all -20 -- path/to/module/ # Who works on this area most git shortlog -sn -- path/to/module/ # When a specific function was introduced git log -S "functionName" --oneline -- path/to/module/ ``` ### Trace a Function's History ```bash # When was this function introduced? git log -S "export function calculateTotal" --oneline # Who has modified it? git blame path/to/file.ts -L 10,30 # What was the commit message? git show <commit-hash> --no-patch ``` ### Find Related Changes ```bash # Files changed together in the same commits git log --all --name-only -- path/to/changed/file.ts | head -20 # Find commits that reference a ticket or pattern git log --all --grep="fix|bug|hotfix" --oneline -20 ``` ### Using `sem` for Deeper Analysis ```bash # Entity-level blame (function level) sem blame path/to/file.ts --function processOrd...