REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
This repo is a collection of 12 skills
✨ Cross-agent skills that help coding agents use Entire context from Checkpoints, sessions, and git history to search past work, explain code, and hand off sessions.Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/entireio-skills)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
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
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser skills | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Anbieter | entireio | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 12 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 240 | 467.235 | 234.125 | 149.873 | 144.332 |
| Letzte Codeänderung | 15. Nov. 2026 | 18. Nov. 2026 | 20. Apr. 2026 | 18. Nov. 2026 | 18. Nov. 2026 |
| Lizenz | MIT | MIT | – | Apache-2.0 | MIT |
12 Skills (Anweisungssammlungen) von entireio, die eine KI liest und befolgt · kein MCP-Server
Install only the ones you use. Open a skill to see how to install it
If you want every one, let the AI install them in one go. Know 2 things first
Uploading to Claude on the web and apps: you need 12 uploads, one ZIP per skill. Open each skill in the list below to download it
Checked against official docs 12. Nov. 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` s…
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "…
Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay ", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week"
Review code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff. Use when the user asks for a code review, wants to review branch changes, or asks to audit recent work before merging.
Use when the user asks to research, investigate, look into, dig into, or search for anything — a topic, feature, bug, decision, or "what do we know about X". Invoke this as the FIRST action on such requests, before Glob, Grep, or Read: the answer is in Entire's recorded history (prompts, transcript…
Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.
Use when the user wants to continue work from one agent in another agent, inspect recent sessions, or summarize a saved session or checkpoint for handoff
Use when the user wants to turn one or more Entire-tracked sessions, checkpoints, or repeated agent workflows into a reusable agent skill.
Use when a developer wants a topic-focused guided lesson built from canonical checkpoints, not a whole-repo overview. Triggers on phrases like "teach me ", "teach me how this repo handles", "how does work in this repo", "give me a lesson on", "school me on", and "I need to learn about"
Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why is this like this" — before Glob, Grep, or Read. Recorded intent lives in Entire checkpoints on the s…
Explain why code looks the way it does by tracing the latest change for a file range or pasted snippet through `git blame` and deduplicated `entire checkpoint explain` lookups. Use when the user asks what happened, says "tell me why" about a code block, is confused about a section of code, asks "wt…
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude CodeCodexCursorGemini CLIGitHub CopilotOpenCode
Laut README des Anbieters und den Ordnern im Repo
This repo has 12 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Schon installiert? Zuerst prüfen · Öffne das Terminal, gib diesen Befehl ein und drücke Enter
node -vMac: ⌘ + Leertaste drücken, Terminal eingeben, Enter
Windows: Start öffnen, Windows PowerShell eingeben, dann Öffnen
Noch nicht installiert: Öffne die offizielle Download-Seite, wähle die LTS-Version und den Klick-Installer: .pkg auf dem Mac · .msi unter Windows. Doppelklicken und bis zum Ende durchklicken. Kein curl-Befehl nötig
Download-Seite von Node.js öffnen ↗
Danach das Terminal schließen, neu öffnen und denselben Befehl erneut ausführen. Es muss eine Versionsnummer erscheinen: node -v
Einmal installieren, gilt für alles, was Node.js braucht
Befehle werden geprüft · Kopier-Buttons erscheinen, sobald sie bestanden sind
Aus dem README des Anbieters; lädt den Code des Anbieters herunter und führt ihn aus
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.