history

Blame data shows the author and commit for every line in a file. Use blame_file() with your file path to get structured authorship history, revealing exactly who modified each line and when, enabling precise code review and accountability tracking.

This Skill provides structured git history as queryable data, not text. Access commits, authorship, and changes through tools like commit_info() and file_history() that return organized results ready for analysis or downstream processing without manual parsing.

Yes. Use changed_symbols() to identify when functions entered the codebase and blame_file() to see the author. Combined, these tools reveal the exact commit and person responsible for introducing any symbol across branches.

Branch_diff() and diff_file() provide semantic diffs showing structural changes between branches. Get precise impact analysis and code review data without manual diff parsing, supporting technical requirements for change tracking and debugging.

This Skill wraps git blame, history, commits, diffs, and status into structured tools: blame_file, file_history, recent_changes, commit_info, search_commits, diff_file, branch_diff, changed_symbols, git_status, git_add, and git_commit. Auto-detects git root from any subdirectory.

No. This Skill handles parsing internally and outputs structured, actionable data suitable for downstream RAG ingestion and code reasoning. Access organized commit, authorship, and diff results directly without text manipulation.