code-import

Generate a normalized repository structure snapshot for efficient agent-based code analysis and migration.

93.2k|10.8k|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/nexu-io/open-design --skill code-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-import
Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/code-import
Command: npx skills add https://github.com/nexu-io/open-design --skill code-import

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the inefficiency of repeatedly walking large codebases during agent operations by creating a persistent, lightweight index of the repository structure.

Core Features & Use Cases

  • Normalized Indexing: Generates a structured JSON snapshot of files, dependencies, and framework configurations.
  • Performance Optimization: Enables agents to perform analysis without re-scanning the entire file tree on every turn.
  • Use Case: When migrating a large monorepo, use this Skill to create a project map that allows the agent to quickly locate components, routes, and metadata without redundant disk I/O.

Quick Start

Run the code-import skill on the current repository path to generate the project index.

Frequently Asked Questions about code-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I index a repository for agent analysis?

Use the code-import skill to scan your repository and generate a code/index.json file. This snapshot provides the agent with a persistent map of your project structure, dependencies, and framework configuration.

What does the code-import skill actually index?

The skill indexes file paths, file sizes, language types, and import statements. It also detects framework-specific configurations, routing models, and component definitions to provide a comprehensive project overview.

Does code-import scan node_modules or build directories?

No, the walker explicitly excludes directories like node_modules, .git, .next, and dist to maintain performance and focus on source code. Skipped paths are recorded in the index for transparency.

When should I re-run the code-import skill?

Re-run the skill whenever the repository structure changes significantly, such as after adding new modules, changing framework dependencies, or performing major refactoring that alters the project's architectural layout.