architecture-review

Automate architectural guardrail, drift, and ADR impact validation on code changes.

3|3|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/PaloAltoNetworks/shifter --skill architecture-review-paloaltonetworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/PaloAltoNetworks/shifter/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/PaloAltoNetworks/shifter --skill architecture-review-paloaltonetworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines architectural reviews to prevent drift, weaken guardrails, and manage ADR impact, ensuring code quality before shipping.

Core Features & Use Cases

  • Cross-Layer Boundary Enforcement: Checks for correct layer boundaries to avoid code interdependencies.
  • Guardrail Integrity Validation: Validates integrity of guardrails such as workflows and configuration files.
  • ADR Impact Assessment: Analyzes changes for existing Architectural Decision Records impact.
  • Shared/Public Seams Auditing: Inspects shared seams to ensure consistent documentation and testing.
  • Use Case: Incorporate into your codebase's pre-commit checks or CI pipeline for immediate feedback on potential issues.

Quick Start

Run the architecture-review skill on your pending commit to validate its impact on the architectural drift and guardrails.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I automate architectural guardrails validation in a CI/CD pipeline?

Automating architectural guardrails validation involves running scripts against your local repository to check code changes for boundary violations, workflow integrity, and ADR impact before shipping. This ensures code quality and prevents architectural drift in your pipeline.

What is architectural drift and how do I check for it in my codebase?

Architectural drift occurs when code changes weaken established design boundaries or guardrails. You can check for it by running architectural review scripts on pending commits to validate cross-layer boundaries, shared seams, and configuration integrity against your repository.

Can I assess Architectural Decision Records impact automatically on code changes?

Yes, you can assess ADR impact automatically by executing architectural review checks against pending commits. This analyzes how code modifications affect existing Architectural Decision Records and validates guardrail integrity within your local repository.

How do I enforce cross-layer boundary checks to avoid code interdependencies?

Enforcing cross-layer boundary checks requires validating correct layer separation within your codebase. Architectural review scripts inspect pending commits to detect interdependencies, ensuring code quality and preventing architectural drift before changes are shipped.

Does architectural review work without external dependencies in my software engineering pipeline?

Yes, architectural review operates without external dependencies. It utilizes internal scripts to execute checks directly against a local repository, validating guardrails, drift, and ADR impact independently within your software engineering pipeline.

When do I need to audit shared seams for documentation and testing consistency?

Auditing shared seams is necessary when validating code changes to ensure consistent documentation and testing across public interfaces. Architectural review scripts inspect these seams to maintain guardrail integrity and prevent architectural drift.