AI tool comparison
git-why vs Matt Pocock Skills
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
git-why
Persist AI agent reasoning traces alongside your code in git history
75%
Panel ship
—
Community
Free
Entry
git-why is an open-source tool that captures and stores the reasoning trace from AI coding agents — the planning, consideration, and decision-making behind code changes — as structured metadata alongside your git commits. Its premise: when you use Claude Code or another AI agent to write code, you produce two artifacts. The code survives in git. The reasoning doesn't. git-why fixes that. The workflow integrates into your existing git hooks. When you commit, git-why serializes the agent's reasoning trace (captured via hooks into Claude Code, Cursor, or Amp) and stores it as a lightweight sidecar file in your repo or a companion metadata store. Future developers (or future you) can run git why <commit-hash> to see not just what changed, but why the AI made the architectural decisions it did — which alternatives it considered, which constraints it was responding to, and what it was uncertain about. The project showed up on Hacker News today and generated thoughtful discussion about AI-assisted development archaeology — the question of how future teams will understand codebases built by AI agents. git-why is the earliest serious attempt at answering that question.
Developer Tools
Matt Pocock Skills
21+ battle-tested Claude agent skills from TypeScript's top educator
75%
Panel ship
—
Community
Free
Entry
Matt Pocock — known for Total TypeScript and beloved among frontend developers — has published his personal directory of Claude agent skills straight from his own `.claude` directory. The repository contains 21+ modular skills organized across four areas: Planning & Design (to-prd, to-issues, grill-me), Development (tdd, triage-issue, improve-codebase-architecture), Tooling (setup-pre-commit, git-guardrails-claude-code), and Writing & Knowledge (edit-article, ubiquitous-language, obsidian-vault). Installation is a single command — `npx skills@latest add mattpocock/skills/[skill-name]` — and each skill is a self-contained module that plugs into Claude Code or similar agent runners. The repository blew up on GitHub trending today with 857 stars, reflecting how hungry developers are for curated, production-tested skill templates from people who actually use them daily. What makes this different from generic awesome-lists is the editorial voice — these are skills Pocock actually uses in his content production workflow. The `edit-article` skill, `write-a-skill` meta-skill, and `obsidian-vault` integration reflect real non-code use cases that most developer-focused skill repos ignore entirely. MIT licensed.
Reviewer scorecard
“The commit message has always been inadequate documentation and AI-generated code makes this worse, not better. git-why is the first tool I've seen that treats agent reasoning as a first-class artifact of the development process. This is especially valuable for onboarding — imagine joining a codebase and being able to ask 'why does this function exist?' and getting the actual AI's reasoning chain.”
“The TDD skill and git-guardrails-claude-code alone are worth the install. Pocock's skills reflect how a TypeScript professional actually works — not generic demo code. The npx install pattern is elegant and composable.”
“The reasoning traces captured by AI agents are often verbose, self-referential, and not actually representative of the true 'why' behind a decision — they're post-hoc justifications as much as genuine reasoning. git-why could end up storing a lot of confident-sounding noise that misleads future developers. Also, the repo size implications of storing detailed traces for every commit need serious consideration.”
“This is one person's personal workflow, not a maintained framework. Skills will drift as Claude updates and Pocock's priorities shift. You're better off building your own SKILL.md files once you understand the pattern.”
“As AI writes an increasing fraction of production code, the question of 'why does this codebase look this way' becomes critically important for maintenance, auditing, and regulatory compliance. git-why is early and rough, but it's pointing at something that will eventually become mandatory for AI-generated code in regulated industries.”
“When influential developers publish their agent workflows publicly it accelerates the entire ecosystem's skill vocabulary. This is how best practices emerge — through high-signal personal repos from trusted practitioners.”
“The concept translates beautifully to creative work — imagine version control for design decisions with the AI's reasoning about why it chose this color palette or layout attached. git-why for Figma would be genuinely revolutionary. The core insight here is timeless: preserve the intent, not just the artifact.”
“The edit-article and ubiquitous-language skills are gems for anyone who writes documentation or content alongside code. Having a creator's perspective embedded in a developer's skill repo is refreshingly rare.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.