Comprehension gate for AI-generated code before shipping

What to build

A pre-commit/CI hook (CLI + GitHub Action) for solo developers and small teams using Cursor, Copilot, or Claude Code that auto-generates a short comprehension quiz on each AI-written diff and blocks the commit or merge until the author passes it, with a simple dashboard tracking understanding scores over time.

AI coding assistants let developers ship code they never actually read; a comprehension-gating hook that quizzes you on your own diff before it ships turns 'I trust the AI' into 'I can prove I understood it' — and the Show HN reception shows builders are hungry for this.

Demand

Solo devs and small teams shipping fast with Cursor/Copilot/Claude Code are increasingly worried about merging code they can't explain, especially after incidents where unreviewed AI code broke production; the strong Show HN reception signals this anxiety is widespread right now.

• Hacker News (Show HN post)News

  Show HN: Sphinx – A hook that quizzes you on your AI's code before shipping — 242 points, 85 comments on HN; described as FOSS and pluggable into existing workflows, indicating high organic engagement for a comprehension-gating tool.

• Hacker News comments (implied)Other

  85 comments on a single Show HN post is a high discussion-to-point ratio, typically signaling a contested, relatable pain point (shipping AI code nobody understands) rather than passive upvoting.

Stack

• Git pre-commit/pre-push hooks (Husky or native git hooks)
• GitHub Actions / GitLab CI
• OpenAI or Anthropic API (to generate quiz questions from a diff)
• tree-sitter or git diff parsing for code context extraction
• Supabase or SQLite for storing quiz results and scores
• Next.js + Vercel for the scores dashboard

Solo + AI difficulty

The core loop (diff in, LLM-generated quiz question out, pass/fail gate) is a weekend build with AI assistance; the hard parts are generating questions that are genuinely hard to guess without understanding the code, keeping latency low enough that devs don't bypass it, and avoiding false positives on trivial diffs. Realistic time-to-MVP CLI is 1-2 weeks; the dashboard and team-score tracking add another 1-2 weeks.

Entry threshold

Buildable solo in days as a git hook or GitHub Action wrapping an LLM call to generate questions from the diff; main effort is packaging, IDE/CI integrations, and distribution rather than core tech complexity.

Window

6-12 months

Where to find first users

• Show HN / Hacker News launch (the category already proved it works)
• r/ExperiencedDevs and r/programming threads on AI code review risk
• Indie Hackers and Product Hunt launch
• Cursor/Claude Code community Discords and forums

Competitors

• Sphinx

Counter-signals & risks

• Developers may game or rush through comprehension quizzes without genuinely engaging, undermining the tool's core value proposition.

• Adding a quiz step introduces friction that time-pressured teams may disable or bypass, similar to how linters/pre-commit hooks are often skipped with --no-verify.

• Larger engineering organizations may prefer built-in AI-review features from Cursor/Copilot/Claude Code vendors rather than adopting a third-party point solution, limiting the addressable market to solo devs and small teams.