code-review

To enforce architectural boundaries during PR reviews, validate that routes and handlers exclusively call the service facade, ensuring no direct database access occurs outside the designated service layer.

Validate TypeScript discipline in a pull request by enforcing strict typing across all modules, requiring explicit ESModule imports, and rejecting any type suppressions or bypasses.

The best way to check for secure database operations is to verify that all queries are parameterized, database client handling is properly managed, and comprehensive error management is implemented.

Ensure MCP protocol compliance by validating that tool definitions are correctly structured, arguments are rigorously validated, and response formats strictly match the expected MCP protocol standards.

Yes, the code review checklist covers authentication scopes by enforcing specific auth scopes for both write and read endpoints, alongside verifying safe token usage across the application.

Embedding tasks should be non-blocking to prevent performance bottlenecks in backend architectures, ensuring they gracefully degrade and do not disrupt primary application workflows under load.