Skip to main content
Knowledge Center

Repo Wiki

Generate repository knowledge and make it available to Qoder tasks.

Repo Wiki turns a code repository into structured project knowledge. Use it when you need to understand architecture, trace an implementation, assess change impact, or help a new contributor learn the codebase.

Find a repository

  1. Select Knowledge Center in the sidebar.
  2. Open the Repo Wiki tab.
  3. Search for the repository, then use Generation Status to show All, Generated, or Not generated projects.
  4. Switch between Grid view and List view when that makes the list easier to scan. Select Refresh to reload status.

Generate Repo Wiki

  1. Open a repository that is marked Not generated, or select Go to generate.
  2. Choose English or 简体中文 under Language.
  3. Review the generation options:
    • Auto Update incrementally refreshes the Wiki when code changes.
    • Auto Export exports Markdown after generation.
    • Citation lets agents use the generated knowledge as task context.
  4. Select Generate Repo Wiki.
Generation runs against the selected codebase. Before starting, check that the repository contains the branch, code, and project documentation you want the Wiki to explain.

Use it in a task

Open a task in the same workspace and state the question or change clearly. Useful prompts include:
  • Explain how a request moves through the main modules.
  • Locate the implementation and callers of a feature.
  • Summarize dependencies and likely impact before a change.
  • Identify repository conventions that should guide an implementation.
Repo Wiki provides project context, but runtime behavior can still differ from documentation. Confirm critical conclusions against current code, configuration, tests, and runtime output.

Keep the result useful

  • Keep source code and repository documentation current.
  • Exclude generated output, dependencies, caches, and unrelated paths from workspace indexing.
  • After material repository changes, check the Repo Wiki status and update the generated knowledge.
  • Ask a representative architecture or implementation question after generation to confirm that the expected context is available.
Do not put credentials, personal data, or restricted information in repository documentation. Repo Wiki can only be as safe and accurate as the content available to the current workspace.