
GitWhy
The shared AI context engine for git
30 followers
The shared AI context engine for git
30 followers
GitWhy is the shared AI context engine for git that captures the prompt, reasoning, decisions, and changed files from Claude Code, Cursor, and other coding agents, tied to the commits that produced them. Share that context with your team and surface it directly in GitHub PRs for faster, clearer reviews.
This is the 2nd launch from GitWhy. View more

WhySpec
Launching today
WhySpec is a spec-driven development framework with "reasoning" layer for AI coding agents: an open-source CLI and agent skill set that helps you plan before coding, capture what actually happened after coding, and preserve the why behind each change for future chats, debugging, and reviews. MIT licensed, works offline, no account needed. Works with Claude Code, Cursor, Copilot, Codex CLI, and more.




Free
Launch Team / Built With



Hey Product Hunt! 👋 I’m Quan, solo-founder of GitWhy.
Today we’re launching our first open-source project: WhySpec.
We built WhySpec because most AI development workflows today — even strong ones like OpenSpec, GSD, and gstack — still don’t preserve the Decision Bridge. They help you plan, execute, and debug, but the reasoning behind the current session usually disappears once the coding is done.
So we built a spec-driven context engineering framework that preserves that "why" from coding agents for future chats, future debugging, and future reviews.
WhySpec is the spec-driven development framework with reasoning layer for AI coding agents: an open-source CLI and agent skill set that helps you plan before coding, capture what actually happened after coding, and track the delta between the two. We call that the Decision Bridge — the gap between the decisions you expected to make and the ones you actually made.
It’s MIT licensed, works offline, needs no account, and is built to work across tools like Claude Code, Cursor, GitHub Copilot, Codex CLI, Windsurf, and more.
My goal with WhySpec is simple: make the reasoning behind code visible, searchable, and durable — especially in a world where agents write more and more of the implementation.
If this resonates, I’d really love your feedback, questions, and tough critiques in the comments. Thanks for checking out WhySpec 💛
Get started: npm install -g @gitwhy-cli/whyspec