AI tool comparison
git-why vs Skills (mattpocock)
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
Skills (mattpocock)
Real-world agent skills for engineers — install via npm, not vibes
75%
Panel ship
—
Community
Free
Entry
Skills is a curated library of AI agent prompts and workflows for real software engineering, created by TypeScript educator Matt Pocock. The project trended to 28,000 GitHub stars with its blunt tagline: "Agent skills for real engineers — not vibe coding." It's a deliberate pushback against chaos-first AI coding in favor of structured, methodical engineering. The library organizes into four categories: Planning & Design (to-prd for converting conversations into PRDs, grill-me for stress-testing plans), Development (tdd for test-driven AI assistance, triage-issue for bug investigation), Tooling & Setup (pre-commit hooks, git safety guards), and Writing & Knowledge (documentation utilities, Obsidian integration). Each skill installs with a single npx command — npx skills@latest add mattpocock/skills/tdd — and plugs into Claude agent setups. With 28,000 stars and 2,200 forks after trending on GitHub on April 27, 2026, Skills has clearly struck a nerve. It's as much a cultural statement as a product: AI coding tools should be used deliberately, with tests, with planning, and with guardrails. The TDD and triage-issue skills address real gaps in how current AI coding agents handle existing codebases rather than greenfield projects.
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 alone is worth the install. Watching a Claude agent plan tests before writing implementation is exactly how I want AI to assist me. Matt's framing of 'real engineering vs. vibe coding' is the right cultural correction for 2026.”
“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.”
“These are sophisticated markdown prompts, not magic. If you're already a disciplined engineer, the skills add ceremony without much acceleration. The 28K stars partly reflect Matt's Twitter following — evaluate the actual skills before star-chasing.”
“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.”
“Community-curated skill libraries installed via package managers will become standard infrastructure — as natural as installing a linting config. Skills is the early prototype of a skills ecosystem that will matter at scale.”
“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 writing and knowledge skills are underrated. The article-editing and Obsidian integration skills bring structured AI assistance to documentation workflows that most agent tools ignore entirely. Install even if you're not primarily a developer.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.