project-knowledge-check

To assess implementation risks before codebase changes, analyze module boundaries across ingestion, retrieval, and MCP workflows to detect knowledge gaps and pinpoint high-risk areas requiring targeted validation.

A maintainer workflow knowledge check for refactoring validates cross-module reasoning by mapping module boundaries, inspecting likely failure points, and planning the safest verification path to reduce implementation blind spots.

Identify knowledge gaps in MCP server and tracing architectures by reviewing how major modules interconnect, surfacing incomplete understanding and missing assumptions about unclear implementation details during code reading.

Yes, you can use architecture review to find high-risk change areas in retrieval workflows by applying test-aware validation and prioritized risk reporting to recommend targeted tests for specific modules.

The best way to plan validation steps for an ingestion module refactor is to confirm module boundaries, inspect likely failure points, and prioritize the highest-value tests to verify cross-module reasoning and reduce change risk.

Yes, this codebase analysis approach works for onboarding reviews of evaluation workflows by checking how major modules interconnect and detecting incomplete understanding to ensure accurate cross-module reasoning during maintainer assessments.