antivibe
A Claude Code skill that makes you read the code it wrote.
Problem
Vibe coding produces working software and zero understanding. You ship a feature, the tests pass, and three weeks later nobody on the team, including the person who prompted it, can explain why the code is shaped the way it is. The learning that used to come free with writing code stopped arriving.
Approach
- Attach to the moment the work finishes, not to a separate 'go learn' ritual nobody performs.
- Explain the code that actually exists in the repo, not a generic tutorial about the framework.
- Go deep enough to be uncomfortable, mapping the patterns to the underlying CS concepts rather than narrating the diff.
Architecture
Trigger
Hooks into the SubagentStop and Stop lifecycle events so the deep-dive fires automatically once a task completes.
Pipeline
A phase-aware explanation pipeline that dispatches subagents and shell scripts to analyse structure, then maps observed patterns to their underlying concepts.
Output
Structured Markdown guides covering design decisions, the alternatives that were rejected, and curated follow-up reading, all of it language and framework agnostic.
Decisions
Automatic, not opt-in
A skill you have to remember to run is a skill nobody runs. Hook integration was the difference between a demo and a habit.
Audit over tutorial
Generic explanations are already a search away. The value is in explaining this repository, with its actual constraints and its actual mistakes.
Outcome
- Over a thousand GitHub stars and 70+ forks, with steady installs from developers auditing AI-written code.
- Selected for the Mintlify OSS Program.
- Works across any language or framework, because the analysis is structural rather than syntactic.