git-history

Analyze per-directory git history, PR descriptions, and blame data to categorize codebase insights.

8|1|Updated Jan 21, 2026

Search Tags:#git #history #pitfalls #contracts #AGENTS.md #architecture-decisions #entry-points

Ready to run

npx skills add https://github.com/orban/intent-layer --skill git-history

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-history
Source: https://github.com/orban/intent-layer/tree/main/skills/intent-layer/git-history
Command: npx skills add https://github.com/orban/intent-layer --skill git-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures tacit knowledge embedded in Git history by extracting insights from commit messages, PR descriptions, and blame data to populate Intent Layer nodes.

Core Features & Use Cases

Extract pitfalls from bug fixes and issues described in commits to guide AGENTS.md content.
Surface architecture decisions and invariants from refactors and migrations.
Identify entry points and critical changes that indicate new capabilities or contracts.

Quick Start

Use git-history to analyze a directory's history and surface actionable insights. For example:

git log --since="1 year ago" --pretty=format:"%h|%s|%b" -- path/to/directory
git log --since="1 year ago" --grep="refactor|BREAKING|migration|fix" -i --pretty=format:"%h|%s" -- path/to/directory

Frequently Asked Questions about git-history

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

FAQPage Schema

How do I extract tribal knowledge from git history to document project pitfalls?▼

To extract tribal knowledge from git history, analyze per-directory commit messages, PR descriptions, and blame data to identify pitfalls, architecture decisions, contracts, and entry points with concrete commit references.

What is the best way to find architecture decisions and invariants in past git commits?▼

Finding architecture decisions in git commits involves filtering history for refactors, migrations, and breaking changes, then categorizing the extracted invariants into a reproducible workflow for Intent Layer nodes.

How does analyzing git blame data help uncover codebase entry points and contracts?▼

Analyzing git blame data surfaces critical changes and new capabilities by tracking per-directory commit history, identifying entry points and contracts that indicate established project boundaries.

Can I use git history analysis to generate AGENTS.md content for my repository?▼

Yes, you can use git history analysis to generate AGENTS.md content by extracting pitfalls from bug fixes and issues described in commits to guide the documentation of tribal knowledge.

What git commands extract commit messages and PR descriptions for knowledge surfacing?▼

Commands like git log with --since and --pretty=format flags extract commit hashes, subjects, and bodies, while grep filters for refactor, breaking, or fix keywords to surface actionable insights.

Does this git history analysis approach work without external dependencies or components?▼

Yes, this git history analysis approach works without external dependencies, relying solely on standard git commands to process local repository commit data and output categorized insights.