antivibe
A Claude Code skill that makes you read the code it wrote.
Shell · Claude Code · MCP
Part of the Mintlify OSS Program
View sourceThe 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.
The 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.
Inside the system
Trigger
Run /antivibe or ask for a deep dive or audit. Optional SubagentStop and Stop hooks suggest the command after code changes; they do not generate a guide on their own.
Pipeline
Phase-aware scripts and guidance inspect repository structure, then connect observed patterns to the concepts behind them. Optional agents can help with larger audits.
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 and trade-offs
A prompt at the right moment
The included hooks remind a developer to run /antivibe after code changes. Keeping guide generation explicit gives the developer control over when analysis runs.
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.
What it produces
- 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.