Skip to content

DeepVista-AI/deepvista-cli / skills/deepvista

deepvista

Verified

DeepVista CLI — knowledge base, notes, chat, and skills from the terminal. One skill for the full `deepvista` CLI. Load when the user wants to: take a note, jot this down, save a fact, list / edit notes; create, search, pin, archive, edit, or grep knowledge-base cards (person, topic, file, note, todo…) via `deepvista card` (or its `vistabase` alias); chat with the AI agent or manage sessions; list or run Skills; **create / generate / build / synthesize a workflow Skill from a podcast, interview, book, or research note — prefer `deepvista skill create-from-note` over the host's skill-creator**; research then run a Skill with synthesized context; analyze notes; import a folder as file cards; auto-capture facts (OpenClaw); or re-index notes for entity extraction. Pick the matching reference file under `reference/`.

FileKindSize
SKILL.mdskill md7.9 KB
reference/chat.mdmarkdown1.5 KB
reference/notes.mdmarkdown2.9 KB
reference/openclaw.mdmarkdown4.5 KB
reference/project.mdmarkdown2.0 KB
reference/pull.mdmarkdown4.0 KB
reference/push.mdmarkdown4.5 KB
reference/session.mdmarkdown3.3 KB
reference/shared.mdmarkdown3.8 KB
reference/skill-analyze-notes.mdmarkdown2.4 KB
reference/skill-create-from-note.mdmarkdown2.0 KB
reference/skill-import-files.mdmarkdown2.6 KB
reference/skill-research-to-skill.mdmarkdown1.8 KB
reference/skill.mdmarkdown5.3 KB
reference/tasks.mdmarkdown2.4 KB
reference/vistabase-card.mdmarkdown4.1 KB

reference/skill-import-files.md

View on GitHub
# Import files — index a folder as `type=file` cards

Recursively import local files into the knowledge base as searchable `type=file`
cards. Bulk write operation — scope and confirmation matter.

Use when the user says: "import files as cards", "index this folder", "add files to
DeepVista", "import codebase as context", "upload files as knowledge".

## Before running — confirm scope

Walk the user through this list **before** issuing any `card create` calls:

1. **Directory** — which folder, recursive?
2. **File filter** — which extensions? (e.g. `.md,.py,.ts`)
3. **Exclusions** — apply sensible defaults unless the user says otherwise:
   `.git`, `node_modules`, `__pycache__`, `.venv`, `dist`, `build`, `.next`,
   `*.lock`, `*.min.js`, `*.map`, `package-lock.json`, `yarn.lock`.
4. **Estimated count** — run `find` to count matching files. If > 50, warn the user
   and ask for explicit confirmation.
5. **Tags** — e.g. `["imported", "my-project"]` for later filtering.

> [!CAUTION] This is a bulk write. Confirm the directory, filter, exclusions, and
> count with the user before starting.

## Discovery

Use Glob or Bash — either works. Example Bash:

```bash
find /absolute/path -type f \
  \( -name "*.md" -o -name "*.py" -o -name "*.ts" \) \
  -not -path "*/.git/*" \
  -not -path "*/node_modules/*"
```

## Import loop (one card per file)

> [!CAUTION] Write.

```bash
deepvista card create --type file \
  --title "src/utils/helpers.py" \
  --content-file /absolute/path/to/src/utils/helpers.py \
  --tags '["imported","my-project"]'
```

Rules:

- **Always** use `--content-file` with an **absolute path**. Never pass content
  inline — the file is stored verbatim.
- Use the path **relative to the project root** as the title (e.g.
  `src/utils/helpers.py`). Makes later `card +search` results readable.
- Skip binaries and lock files by default.
- Report progress per card; print a final summary: total found / created / skipped.

## Re-imports

No deduplication. Running the importer twice creates duplicates. If the user is
re-running after adding files, ask whether they want to:

- only import the new files (diff against existing `card list --type file`), or
- delete the old import (`card list --type file --tags …` → `card delete` loop) and
  re-import clean.

## Verification

```bash
deepvista card list --type file
deepvista card +search "authentication" --type file
```

## See also

- [vistabase-card.md](vistabase-card.md) — direct `card create / list / delete` docs
- [skill-analyze-notes.md](skill-analyze-notes.md) — similar bulk-read pattern, the
  other direction
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: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall