architecture-strategist

Analyze code changes for architectural compliance and design integrity.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill architecture-strategist-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-strategist
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/architecture-strategist
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill architecture-strategist-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides systematic, architecture-focused analysis of code changes to ensure modifications align with established design patterns, maintain component boundaries, and avoid introducing structural regressions or technical debt.

Core Features & Use Cases

  • Architecture mapping: Extracts architecture context from READMEs, docs, and imports to outline component relationships and service boundaries.
  • Change assessment: Evaluates pull requests, new services, and refactors for coupling, cohesion, circular dependencies, and layering violations.
  • Compliance & guidance: Verifies SOLID principles, API contract stability, and documents recommended remediation with pragmatic trade-offs.

Quick Start

Review the open pull request and produce a structured architecture assessment that lists violations, risks, and concrete remediation steps.

Frequently Asked Questions about architecture-strategist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check code changes for architectural compliance and SOLID principle violations?

Detecting circular dependencies in a microservice codebase involves inspecting component boundaries and evaluating dependency analysis metrics. This reveals structural layering violations across services, ensuring modifications avoid introducing technical debt.

What is the best way to assess structural refactoring risks in a modular monolith?

To evaluate pull requests for system design integrity, inspect component relationships and service boundaries extracted from documentation. This verifies that code changes maintain architectural compliance and avoid structural regressions across the codebase.

Does architectural analysis work for both monoliths and microservice environments?

Architecture mapping extracts component relationships and service boundaries from READMEs, docs, and imports. It outlines the structural context needed to evaluate coupling, cohesion, and layering violations during code reviews.

How do I verify API contract stability and component boundaries when adding new services?

Limitations of architecture-focused code review include its exclusive focus on structural compliance rather than functional testing. It cannot validate runtime behavior or execute code, but instead produces prioritized remediation steps for design violations.