architecture-strategist

To perform an architectural review for a pull request, analyze code changes to ensure they align with established architectures and patterns. The process maps dependencies, evaluates coupling, and proposes concrete improvements to maintain system integrity.

Evaluating code change impact across multiple service boundaries involves tracing dependencies and coupling to identify potential ripple effects. This change impact mapping assesses proposed changes against documented patterns to prevent structural drift.

To ensure code refactors comply with established system design patterns, apply architectural governance during the review process. This suggests concrete architectural improvements and guardrails when introducing new services or modifying boundaries.

Architectural validation for new services is needed when introducing changes across multiple components and boundaries. It enforces architectural integrity by preventing structural debt and ensuring new services align with established patterns.

Yes, analyzing structural debt during code reviews works by mapping dependencies and evaluating coupling. It helps teams ensure code changes comply with established architectures, avoiding structural drift and debt during PR reviews.

Yes, you can use this to suggest guardrails for refactoring across multiple components. It provides guidance for refactors by proposing concrete architectural improvements that maintain integrity across service boundaries.