Ingestion & Summary

Repository content ingestion in Venue.sh indexes source code from your connected Git repositories so your organization can search repository content, generate AI summaries, and discover Skills from SKILL.md files.

Ingestion runs in the background after repositories are imported or updated in the catalog. Administrators configure ingestion and summary generation under Settings > Ingestion & Summary.

Key Capabilities

• Repository indexing - Pull repository content, chunk source files, and build searchable embeddings for your organization.
• AI summaries - Generate structured summaries (purpose, technologies, architecture, and key components) for catalog entities linked to repositories.
• Assistant integration - Let the Assistant answer repository summary and code questions using ingested content.
• Skills discovery - Automatically catalog agent skills from SKILL.md files during ingestion (see Skills).

How Ingestion Works

When repository ingestion is enabled for your organization, Venue.sh starts an ingestion job automatically in these situations:

• You import repositories into the catalog.
• A catalog entity with an associated repository is created or updated.

Each job indexes the repository's source content. When the job completes, search and summary features use the latest indexed snapshot. If ingestion is disabled, new jobs are not started.

Prerequisites

• A Git connection and imported repositories with valid source locations in the catalog.
• Repository ingestion enabled under Settings > Ingestion & Summary.
• For AI summaries, Repository Summary must also be enabled on the same settings page.

Configuring Ingestion & Summary (Admin)

Administrators manage ingestion from Settings > Ingestion & Summary (/settings/ingestion-summary). You need permission to configure Assistant settings to view or update this page.

1. Open Settings and select Ingestion & Summary.
2. Configure Repository Ingestion and Repository Summary as described below.
3. Click Save changes.

Changes apply to future ingestion jobs and summary generation requests.

Repository Ingestion

Use the Repository Ingestion switch to enable or disable indexing for your organization. When you disable ingestion, Repository Summary is turned off as well.

Choose an embedding mode:

Mode	Description
Managed Ingestion	Venue.sh handles repository ingestion and keeps the underlying embedding configuration out of the way. Recommended for most organizations.
Bring Your Own Model	Connect a self-hosted Ollama embedding endpoint. Provide the Ollama Base URL, Model Name, and an API Key if your endpoint requires authentication.

Other embedding options

If you want to use a different embedding providers such as Voyage AI or Cohere, please reach out to the Venue.sh team.

Repository Summary

When Repository Ingestion is enabled, you can turn on Repository Summary to generate AI summaries for indexed repositories.

By default, Venue.sh uses Managed Summary and creates summaries automatically after ingestion completes.

Under Advanced, you can enable Use Assistant Configuration and select an existing Assistant configuration and model for summary generation. You must have at least one Assistant configuration with allowed models before using this option (see Setting Up the Assistant (Admin)).

Viewing Repository Summaries

When a summary exists for a catalog entity linked to a repository, a Summary tab appears on the entity detail page (after Overview).

The summary includes:

• Purpose - What the repository or service does.
• Technologies - Languages, frameworks, or tools detected in the codebase.
• Architecture - High-level structural overview.
• Key components - Notable modules or areas of the codebase.
• Conventions - Coding or repository conventions when available.

If no summary tab appears, the repository may not be ingested yet, summary generation may be disabled, or a summary has not been generated for that repository.

Using Ingestion with the Assistant

When ingestion is enabled and a repository has been indexed, the Assistant can help with repository-aware questions. For example:

• "Give me a summary of the checkout-service repository."
• "How is authentication implemented in the payments-service repo?"
• "Where is the database connection configured in frontend-app?"

The Assistant resolves repositories by name, URL, or catalog context. You do not need to provide internal repository IDs.

Repository search respects team ownership. You can only search repositories your teams own in the catalog. If you see no results or an access error, confirm your team membership and the entity's owner metadata.

Skills Discovery

During ingestion, Venue.sh scans repository files for SKILL.md definitions and updates the Skills catalog. New or updated skills appear after the next successful ingestion run for that repository. Removed SKILL.md files are dropped from the catalog on a subsequent run.

Permissions

Action	Who can do it
View Ingestion & Summary settings	Users with Assistant settings read access (typically administrators)
Update ingestion and summary settings	Users with Assistant settings create/update access (administrators)
View repository summaries in the catalog	Users with catalog read access to the entity
Search ingested repository content via the Assistant	Users who belong to a team that owns the repository

Ingestion jobs triggered by import or entity updates are recorded in the Activity Log.

Troubleshooting

Situation	What to do
No Ingestion & Summary menu item	Your role may not include Assistant settings access. Contact your Venue administrator.
Ingestion never runs	Confirm Repository Ingestion is enabled and repositories are imported with a valid source location annotation.
No Summary tab on an entity	Enable Repository Summary, wait for ingestion to complete, and confirm the entity is linked to a repository.
Assistant cannot answer code questions	The repository may not be ingested yet, ingestion may be disabled, or you may not have access to that repository's owning team.
Skills not appearing	Wait for the next ingestion run after committing SKILL.md files. Confirm the repository is connected and ingestion is enabled. See Skills.
Ollama mode fails	Verify the base URL, model name, and API key. Ensure Venue.sh can reach your Ollama endpoint from its environment.

See Also

• Importing Repositories - Connect and import repositories into the catalog.
• Assistant - Ask questions about catalog, documentation, and ingested repositories.
• Skills - Browse agent skills discovered during ingestion.
• Activity Log - Audit trail for ingestion events.