Visualize Repo
Open or create a repo-native visual documentation workspace backed by local Plan MDX...
Install
npx skills add BuilderIO/agent-native --skill visualize-repo -g -a claude-code -y- Repository
- BuilderIO/agent-native7.6k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 840 tokens
- Runs scripts
- No, instructions only
What it does
Open or create a repo-native visual documentation workspace backed by local Plan MDX files. Use when the user asks to visualize a repository, create durable visual docs for APIs/components/models/flows, launch a visual repo viewer, review repo docs like a visual IDE, or collect Plan comments that should become coding-agent changes.
Visualize Repo
/visualize-repo opens a local, source-controlled visual documentation layer
for a repository. It is for durable repo understanding, not a one-off plan:
components can have wireframes, APIs can have specs, models can have schema
views, and reviewers can comment on those docs before sending work to a coding
agent.
Default Command
Run the Agent-Native CLI from the repo root:
npx @agent-native/core@latest visualize-repo --open
Useful variants:
npx @agent-native/core@latest visualize-repo init
npx @agent-native/core@latest visualize-repo --target actions --target server/db/schema.ts
npx @agent-native/core@latest visualize-repo check
npx @agent-native/core@latest visualize-repo verify
npx @agent-native/core@latest visualize-repo --no-open
The command writes or updates agent-native.json with an
apps.visualize-repo local-files section, creates a starter MDX folder at
.agent-native/visual-docs/repo-overview, then serves it through the Plan
local bridge. The hosted Plan UI can render the review surface, but the plan
source stays in local files and bridge comments stay in comments.json.
When There Is No Manifest
If agent-native.json does not exist, let the CLI bootstrap one. It scans for
high-value starting points such as actions/, app/components/,
app/pages/, server/db/schema.ts, src/, packages/, templates/,
docs/, and content/. Keep the first run targeted. Prefer 5-20 visualized
nodes over a generated wall of repo prose.
Use explicit targets when the user already knows the important surface:
npx @agent-native/core@latest visualize-repo \
--target actions/webhooks.ts \
--target server/db/schema.ts \
--target app/components/PromptComposer.tsx
