The outcome

Give Qoder accurate project context with clear ownership, access, freshness, and deletion behavior.

Step by step

A workflow you can repeat.

  1. 01

    Inventory repositories, sensitive paths, data owners, permitted users, retention, required knowledge, and questions the context should answer.

  2. 02

    Enable only approved repository knowledge, exclude secrets and generated data, and write short scoped rules linked to canonical documentation.

  3. 03

    Inspect generated Repo Wiki and memory for accuracy, sensitive content, stale branches, unsupported inference, and conflicts with current source code.

  4. 04

    Test retrieval and agent behavior with known answers, missing context, renamed components, hostile documentation, unauthorized questions, and deleted files.

  5. 05

    Assign owners, review access and freshness regularly, correct or remove stale knowledge, and confirm deletion and provider handling when a repository leaves scope.

Working standard

What good use looks like.

  • Index the minimum useful context.
  • Treat source code as more authoritative than generated wiki.
  • Audit memory and deletion behavior.

Official references

Check the current product documentation.