REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Learn what AI writes, not just accept it. A Claude Code skill that turns AI-generated code into educational deep dives.
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/mohi-devhub-antivibe)Servidores MCP que conectan la IA a servicios para el mismo trabajo
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este antivibe | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Autor | mohi-devhub | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| Estrellas de GitHub | 1138 | 465.460 | 233.910 | 149.364 | 144.149 |
| Último cambio de código | 31 jul 2026 | 17 nov 2026 | 20 abr 2026 | 17 nov 2026 | 17 nov 2026 |
| Licencia | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (conjuntos de instrucciones) de mohi-devhub que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Claude Code
Según el README del autor y las carpetas del repo
GitHub account mohi-devhub (person), 2 years old
★ 1138 stars · code last changed 31 jul 2026
4 scripts that can run on a computer: scripts/analyze-code.sh, scripts/capture-phase.sh, scripts/find-resources.sh, scripts/generate-deep-dive.sh
No internet calls found in the scripts
Installing the maker’s way adds hooks that run without you asking: run every time a sub-agent finishes · run every time the AI finishes a reply and adds 2 sub-agents
Checked automatically from the repo files at commit 9991d12 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Uploading to claude.ai would fail: the description is over 200 characters (238). Use "Let the AI install it" instead
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /antivibe, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/mohi-devhub/antivibe.git /tmp/popnx-skill-mohi-devhub-antivibe-9991d12 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-mohi-devhub-antivibe-9991d12/.' ~/.claude/skills/antivibeLa app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Coloca la carpeta antivibe en ~/.agents/skills/antivibe
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/mohi-devhub/antivibe.git /tmp/popnx-skill-mohi-devhub-antivibe-9991d12 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-mohi-devhub-antivibe-9991d12/.' ~/.agents/skills/antivibeChecked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/mohi-devhub/antivibe.git /tmp/popnx-skill-mohi-devhub-antivibe-9991d12 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-mohi-devhub-antivibe-9991d12/.' ~/.agents/skills/antivibeCopia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige antivibe
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/mohi-devhub/antivibe.git /tmp/popnx-skill-mohi-devhub-antivibe-9991d12 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-mohi-devhub-antivibe-9991d12/.' ~/.cursor/skills/antivibePara otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 18 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: antivibe
description: Code learning and audit framework. Analyze any codebase — new, legacy, or AI-generated — and produce educational explanations or architectural audits. Use when the user wants to understand WHAT and WHY behind any code, not just accept it.
triggers:
- phrase: "/antivibe"
- phrase: "deep dive"
- phrase: "anti-vibecode"
- phrase: "why did AI write"
- phrase: "learn from this code"
- phrase: "understand what AI wrote"
- phrase: "explain what AI wrote"
- phrase: "walk me through"
- phrase: "explain this file"
- phrase: "explain this codebase"
- phrase: "analyze this module"
- phrase: "audit this"
- phrase: "just the trade-offs"
- phrase: "what should I worry about"
- phrase: "code review"
---
# AntiVibe - Code Learning & Audit Framework
## Purpose
AntiVibe generates **learning-focused explanations or architectural audits** of any code — AI-generated, legacy, or otherwise. It helps developers understand:
- **What** the code does (functionality)
- **Why** it was written this way (design decisions)
- **When** to use these patterns (context)
- **What alternatives** exist (broader knowledge)
Works on any codebase — you don't need recent git history or AI-authored files.
## When to Use
Use AntiVibe when:
1. **Manual invocation**: User types `/antivibe` or "deep dive"
2. **Post-task learning**: After a feature/phase completes, user wants to learn from it
3. **Legacy codebases**: User wants to understand existing code they didn't write
4. **Proactive**: User says "explain what AI wrote", "walk me through", "audit this", or points at a file/directory
## What AntiVibe Produces
Output saved to `deep-dive/` folder as markdown:
```
deep-dive/
├── auth-system-2026-01-15.md
├── api-layer-2026-01-15.md
└── database-models-2026-01-15.md
```
The exact sections depend on the output mode (see [Output Mode](#output-mode)):
| Section | `compact` (default) | `full` |
|---------|:---:|:---:|
| **Overview** — what the code does and why it exists | ✅ | ✅ |
| **Key Components / Concepts** — design patterns, algorithms, CS concepts used | ✅ | ✅ |
| **Code Walkthrough** — file-by-file, line-by-line notes | — | ✅ |
| **Learning Resources** — curated docs, tutorials, videos | — | ✅ |
| **Related Code** — links to other files in the codebase | — | ✅ |
## Configuration
### Known Concepts (Skip List)
Concepts listed here will not be explained in full — the explainer will only note that they were used and in what context. Edit this list to match your current knowledge.
```yaml
known_concepts:
- async/await
- React hooks
- REST APIs
```
### Output Mode
Controls how much detail is generated per run. Default is `compact` to keep token costs low.
```yaml
output_mode: compact
```
| Mode | What's included |
|------|----------------|
| `compact` (default) | Overview, key components (function-level, one line each), concepts (what + why only). No resources. No line-by-line. Max 5 files. |
| `full` | Everything in compact, plus: line-by-line walkthrough, prerequisites, curated resources, Next Steps. |
Override inline in your request:
- `"/antivibe full"`, `"full deep dive"`, `"include resources"` → `full` mode
- Default: `compact`
### Default Skill Level
Sets the explanation depth when no level is specified in the request. Options: `junior`, `mid`, `senior`. Default: `mid`.
```yaml
default_level: mid
```
| Level | Behavior |
|-------|----------|
| `junior` | Define all terms. Use analogies. Explain language features. Show full code snippets with inline comments. |
| `mid` | Skip basics. Focus on design decisions and trade-offs. Brief code references only. |
| `senior` | Skip obvious patterns. Focus only on non-obvious choices, edge cases, and architectural trade-offs. |
Level can also be specified inline in the request:
- `"explain for a junior"`, `"I'm new to this"` → `junior`
- `"I know the basics"`, `"mid level"` → `mid`
- `"senior mode"`, `"skip the basics"`, `"just the trade-offs"` → `senior`
---
## Workflow
### Step 0: Apply User Configuration
Before analyzing, read the configuration above:
- Load the `known_concepts` skip list. Any concept in this list will be acknowledged in one sentence instead of fully explained.
- Detect the skill level: check the user's request first (inline phrases take priority), then fall back to `default_level`. Apply this level consistently throughout the entire output.
- If level = `senior`, route to `agents/auditor.md` instead of continuing this workflow.
### Step 1: Identify Code to Analyze
Use the first applicable mode:
1. **Explicit** — User named specific files, a directory, or a module in their request → use those directly. No git needed. Example: "explain `src/auth/`" or "walk me through `api/routes.py`".
2. **Recent** — No explicit target given, project is a git repo, and `git diff HEAD` has output → use those changed files (current behavior for post-AI-task learning).
3. **Scan** — No explicit target, no usable git diff (legacy project, no recent changes, or not a git repo) → ask the user: "Which file, directory, or module would you like to analyze?" Do not attempt to guess.
> The code does not need to be AI-generated. AntiVibe analyzes any code.
### Step 2: Analyze Code Structure
For each file:
- Identify main purpose and responsibilities
- Note key functions, classes, modules
- Identify design patterns used (factory, singleton, observer, etc.)
- Find any complex logic or algorithms
### Step 3: Explain Concepts
For each concept/pattern found:
- **What**: Plain-language explanation
- **Why**: Why this approach was chosen over alternatives
- **When**: When to use this pattern (with context)
- **Alternatives**: Other approaches and trade-offs
- **Prerequisites**: 2–4 foundational concepts the developer must understand first (e.g., "To understand JWT, you need: HTTP request/response, Base64 encoding, cryptographic signing")
### Step 4: Find External Resources
**Only run this step in `full` mode.** Skip entirely in `compact` mode.
Search for and include:
- Official documentation for libraries/frameworks used
- Quality tutorials or blog posts
- Video resources (if available)
- Related concepts for further learning
### Step 5: Generate Output
Create markdown file in `deep-dive/` folder:
- Name format: `[component]-[timestamp].md`
- Detect output mode from the request or `output_mode` config (default: `compact`)
- **Compact mode**: Use the compact template. No line-by-line, no resources, no Next Steps. Max 5 files — if more are in scope, summarize extras in one line each and offer to go deeper.
- **Full mode**: Use the full template from `templates/deep-dive.md`. Include all sections. No 5-file limit — analyze every file in scope; for very large inputs, split the output across multiple deep-dive files rather than truncating.
- Make it educational, not just descriptive
## Auto-Trigger Configuration
AntiVibe can be configured to auto-trigger via hooks:
- **SubagentStop**: After a Task completes a feature
- **Stop**: At session end
To enable auto-trigger, configure hooks in your project (see `hooks/hooks.json`).
## Principles
1. **Why over what** - Always explain design decisions
2. **Context matters** - Explain when/why to use patterns
3. **Curated resources** - Quality links, not random Google results
4. **Phase-aware** - Group by implementation phase
5. **Learning path** - Suggest next steps for deeper study
6. **Concept mapping** - Connect code to underlying CS concepts
## Dependencies
Optional scripts in `scripts/` folder:
- `capture-phase.sh` - Detect implementation phase boundaries
- `analyze-code.sh` - Parse code structure
- `find-resources.sh` - Search for external resources
- `generate-deep-dive.sh` - Create markdown output
These are helpers - you can also do everything via direct code analysis.
## Examples
**Input**: "Explain the auth system Claude wrote" *(recent AI code)*
→ Mode: Recent (git diff). Output: `deep-dive/auth-system-2026-0Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.