houseprice-codebase-research

Cross-repo codebase research traces feature implementations by following the controller→service→repository path to locate exact SQL queries, API calls, enums, and DTOs. It verifies behaviors across develop branches and maps dependencies between affected repositories.

Cross-repo dependency mapping detects URL keys and external calls during codebase research, then generates a blockers-and-questions list. Items are marked 'from code (to verify)' or 'unknown (ask user)' to capture unknowns as verifiable findings instead of informal assumptions.

Codebase research verifies existing schema and enum usage by applying grep-level verification across develop branches. It traces the target endpoint from controller to repository, checking mappings and producing a clear implementation plan for new fields.

Yes, codebase research requires direct repository access and grep-level verification to trace cross-service API calls accurately. This ensures findings reflect verified code paths rather than assumptions when mapping dependencies across repositories.

Update the dependency map during backend feature research when cross-repo dependencies are detected. The process creates CROSS-REPO placeholders for external calls and URL keys, then updates the project mapping to reflect verified dependency relationships.

Codebase research is limited to develop branches and requires grep-level verification for accurate tracing. It cannot resolve items marked 'unknown (ask user)' without additional input, and depends on direct repository access to verify controller→service→repository paths.