lyonzin/knowledge-rag

Before answering any technical question, code request, architecture decision, or factual claim, call searchknowledge to check the local corpus.

lyonzin/knowledge-rag

Every technical claim drawn from the local corpus must ship with a source citation formatted as path:line or path:section.

lyonzin/knowledge-rag

When performing code review on a PR, diff, snippet, or "look at this change" request, first consult the corpus for related ADRs, coding standards, prior patterns, and similar files.

lyonzin/knowledge-rag

Three-step multi-tool workflow — search the corpus, fetch the most relevant document in full, then find similar documents.

lyonzin/knowledge-rag

When the user reports a bug, error message, stack trace, unexpected behavior, or "why is this broken" question, search the corpus first for prior occurrences, known fixes, or related runbooks.

lyonzin/knowledge-rag

Measure retrieval quality using evaluateretrieval (MRR@5 and Recall@5) and getindexstats.

lyonzin/knowledge-rag

After making a non-obvious architectural decision, solving a novel bug, agreeing on a coding standard, or reaching a conclusion worth remembering, index it back into the knowledge base so the next…

lyonzin/knowledge-rag

At the start of every new session or when the topic shifts significantly, probe the knowledge base to learn what is indexed.

lyonzin/knowledge-rag

For any security-related task — threat triage, incident response, MITRE ATT&CK mapping, CVE lookup, exploit analysis, defensive control validation, red/blue/purple team work — always consult the…

lyonzin/knowledge-rag

Only reach for external web search when the local corpus comes back empty or clearly insufficient.

lyonzin/knowledge-rag