Skip to main content

Repo Wikis

ProdE automatically generates comprehensive documentation for every connected repository — we call these Repo Wikis. They give you a structured, always up-to-date reference to understand any repository in your organization inside and out.

What Are Repo Wikis?​

When you connect a repository to ProdE and the Knowledge Layer finishes processing, ProdE automatically generates a detailed wiki for that repository — derived entirely from your source code.

No manual effort is required. ProdE treats your code as the single source of truth and transforms it into a structured, browsable knowledge base.

What's Inside a Repo Wiki?​

Each wiki is tailored to the repository it describes. The content is organized as a navigable hierarchy of feature-based documentation pages:

  • Repository Overview — A high-level summary at the top of the hierarchy covering what the repository does and how it's organized.
  • Feature Groups — Logical groupings of related features (e.g., "Authentication", "Payment Processing", "API Layer"), each with a summary page that brings together documentation from its child features.
  • Individual Feature Pages — Detailed documentation for specific features, including what the feature does, the code symbols that implement it, and how it connects to other parts of the system.

The exact structure varies by repository — ProdE adapts the hierarchy to match the actual features and organization of your codebase.

How to Access Repo Wikis​

  1. Navigate to Documentation in the ProdE sidebar
  2. You'll see a grid of all repositories that have generated documentation, showing the repository name, source, and number of documentation pages
  3. Select a repository to open its wiki

Once inside a repository's wiki, you'll see:

  • A sidebar on the left showing the documentation hierarchy — click any node to navigate to that page
  • The documentation content on the right rendered as Markdown

The wiki is available as soon as the Knowledge Layer finishes processing the repository.

Using Repo Wikis to Understand a System​

Repo Wikis are designed to help you understand a system inside and out — whether you're onboarding, debugging, or planning a change.

Onboarding onto a New Codebase​

Start with the top-level overview page to understand the purpose and structure of the repository. Then browse the hierarchy to find feature groups relevant to your work and drill into individual feature pages to understand the implementation.

Understanding Cross-Service Interactions​

Feature pages document which code symbols are involved and how they connect to other parts of the system. Use this to trace how features span across modules and understand the boundaries between components.

Preparing for a Code Change​

Before modifying a repository, browse the relevant feature pages to understand what exists and how things connect. This helps you identify the right place to make changes and anticipate side effects.

Investigating Bugs​

Navigate to the feature pages relevant to the bug. Each page documents the code symbols involved, making it easier to trace the execution path and understand the data flow through the affected components.

Repo Wikis in Codebase Chat and MCP​

Repo Wiki content doesn't just live in the Documentation page — it powers Codebase Chat and the Codebase Understanding MCP server as well. When you ask questions about your code, ProdE uses the wiki content to provide richer, more accurate answers grounded in your actual codebase.

Automatic Updates​

Repo Wikis stay current with your codebase. When ProdE syncs your repositories (daily), the documentation is updated to reflect the latest state of the code. You always get documentation that matches what's actually in the repository.

Use Cases​

For Developers​

  • Quickly understand unfamiliar repositories without reading every file
  • Find the right module or function to modify for a given change
  • Trace feature implementations across code symbols during debugging

For Engineering Leads​

  • Get a structured overview of any repository in the organization
  • Understand the feature landscape of a codebase at a glance
  • Use wikis as a foundation for architecture reviews and technical discussions

For Product Managers​

  • Understand what a repository does and which features it implements
  • Identify which parts of the codebase are involved in a feature area
  • Get technical context without needing to read source code
Last updated on