← ClaudeAtlas

gitreverselisted

Turn a public GitHub repository into a single synthetic user prompt that someone might paste into Cursor, Claude Code, Codex, etc. to vibe-code the project from scratch. Use when the user references a GitHub URL or `owner/repo` slug together with prompt reconstruction, vibe coding, or rebuild-from-scratch intent. Route source: https://github.com/filiksyos/gitreverse
dmae97/omk · ★ 143 · AI & Automation · score 80
Install: claude install-skill dmae97/omk
# GitReverse — repository to prompt Reverse a **public GitHub repository** into **one short, conversational user prompt** grounded in real repo context. This ports the GitReverse flow (https://github.com/filiksyos/gitreverse) into an OMK skill: pull repo metadata, a depth-1 root file tree, and the README, then synthesize the single prompt a person could paste into an AI coding agent to rebuild the project from scratch. ## Core workflow 1. Parse the target: accept a full GitHub URL (`https://github.com/owner/repo`, including `/tree/...` paths — use the whole repo for now) or an `owner/repo` slug. GitHub-style `tree` subpaths are NOT scoped yet; the reverse flow uses the whole repo. 2. Verify visibility: only **public** repositories. If the repo 404s, is private, or requires auth to read, stop and report it as a blocker. 3. Fetch exactly three evidence surfaces: - repo metadata (owner, name, description, primary language, topics) - root file tree at depth 1 (top-level files and directories) - README (rendered to text) 4. Synthesize **one** short, conversational prompt grounded in that context. It describes what to build, not how to copy it — no file dumps, no verbatim README paste, no system prompts. 5. Cite evidence: name which facts came from metadata vs. file tree vs. README, and keep observed facts clearly separated from synthesized text. ## Tool selection - Tools: `gh` or `git` for local checks; plain HTTPS `fetch` against `api.github.c