history

Extract structured git history and semantic diffs for code analysis.

Updated Aug 23, 2026

Search Tags:#git #commits #history #semantic-diff #blame

Ready to run

npx skills add https://github.com/Technikhighknee/agent-workbench --skill history

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: history
Source: https://github.com/Technikhighknee/agent-workbench/tree/main/.claude/skills/history
Command: npx skills add https://github.com/Technikhighknee/agent-workbench --skill history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning raw git text into structured, actionable history and semantic diffs.

Core Features & Use Cases

Blame data: Author per line for precise history.
Structured history: Commits, symbols, and changes without manual parsing.
Use Case: Identify when a function was introduced and by whom.

Quick Start

blame_file({ file_path: 'src/auth.ts' })

Frequently Asked Questions about history

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

FAQPage Schema

How do I see who changed each line of code in a file?▼

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.

How do I get structured git commit history without parsing raw output?▼

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.

Can I track when a specific function was introduced and by whom?▼

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.

How do I analyze what code changed between two 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.

What git operations does this Skill support?▼

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.

Do I need to manually parse git output to use this Skill?▼

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.