hiivmind-corpus-add-source

To add a new documentation source to your corpus, run the tool in your project directory and follow the CLI-guided prompts to collect source metadata, handle conflicts, and write the new entry into config.yaml.

Corpus content indexing supports git, local, web, Obsidian vaults, llms-txt, generated-docs, and PDFs, applying automatic source typing and extraction configuration during the discovery phase.

Yes, you need a running config.yaml file and repository access to integrate a new documentation source, as the tool requires this environment to validate metadata and write the updated source configuration.

Yes, you can add an Obsidian vault as a recognized source type alongside git, web, and PDFs, enabling semantic search by updating the corpus config with the correct extraction settings.

During source management, the tool provides error handling and uses CLI-guided prompts to resolve conflicts, ensuring the new documentation source is validated before updating the config.yaml file.

The best way to manage web sources and local PDFs in a documentation corpus is using a phase-driven workflow that automates type detection, extraction configuration, and config.yaml updates for efficient indexing.