nexu-io/open-design / plugins/_official/atoms/code-import
code-import
VerifiedRead an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
Code import
Spec §10 / §21.3.2: a code-migration / tune-collab run starts from a
real repo (cloned via od project import or a path the user
provided). This atom turns the raw checkout into a normalised
on-disk record that subsequent atoms (design-extract,
rewrite-plan, patch-edit) operate against. The point is to
stop re-walking the tree on every turn — the agent reads
code/index.json once and trusts the snapshot until the next
explicit re-import.
Inputs
| Source | Required | Notes |
|---|---|---|
repoPath | yes | Absolute path to the repo's root, supplied via od project import or an upstream od.context.assets[] reference |
targetStack | yes | { framework, packageManager, styleSystem, componentLibrary } via the matching form GenUI surface |
Output
project-cwd/
└── code/
├── index.json # { files: { path, size, language, imports[] }[], packageJson?, lockfileKind, framework, styleSystem }
├── components.json # detected components with file path + props snapshot
├── routes.json # detected routing model (next/app, react-router, vite-router, …)
└── meta.json # { repoPath, gitSha, walkedAt, atomDigest, walkBudgetMs }
code/index.json is the input every other Phase 7 atom reads. The
walk respects the runner's budgetMs option (default 60s) so
large monorepos don't burn an entire run on import.
Convergence
The atom completes when code/index.json exists and contains at
least one entry. Empty repos abort with a clear error event so the
user re-imports.
Anti-patterns the prompt fragment forbids
- Walking node_modules / .git / .next / dist / build (record in
code/index.json.skipped[]with reason). - Inferring a framework from a single file; require at least
package.json's declared dep + a build-config presence (next.config.*,vite.config.*, etc.). - Treating commented-out imports as live edges.
Status
Implemented by the daemon runner in
apps/daemon/src/plugins/atoms/code-import.ts. The walker enforces its
exclusions and time budget, detects framework evidence, and writes
code/index.json.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |