reviewing-python-architecture

Review Architecture Decision Records against testing principles and parent PDR constraints.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeengineering/spx-claude --skill reviewing-python-architecture-outcomeengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-python-architecture
Source: https://github.com/outcomeengineering/spx-claude/tree/main/plugins/python/skills/reviewing-python-architecture
Command: npx skills add https://github.com/outcomeengineering/spx-claude --skill reviewing-python-architecture-outcomeengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that architectural decisions, specifically ADRs (Architecture Decision Records), align with established testing principles and project-specific constraints, preventing common pitfalls in software design.

Core Features & Use Cases

  • Principle Enforcement: Verifies ADRs against the /testing methodology, focusing on dependency levels, mocking prohibitions, and the reality principle.
  • Constraint Checking: Ensures ADRs comply with parent PDR (Project Decision Record) constraints.
  • Violation Identification: Clearly points out specific violations, referencing the violated principle and providing corrected architectural examples.
  • Use Case: When reviewing a new ADR for a Python microservice, use this Skill to automatically check if it proposes using mocks for external services or incorrectly assigns dependency levels, ensuring maintainability and robustness.

Quick Start

Review the attached ADR document to ensure it follows the /testing principles and parent PDR constraints.

Frequently Asked Questions about reviewing-python-architecture

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

FAQPage Schema
How do I review Python architecture against testing principles in ADRs?

You review Python architecture by evaluating ADRs against the /testing methodology, focusing on dependency level definitions, mocking prohibitions, and the reality principle. The review identifies specific violations and outputs corrected architectural examples for maintainability.

What is the reality principle in code review for Python architecture?

The reality principle in Python code review is a testing rule enforced during ADR evaluation that prohibits mocking external services. It ensures architectural decisions maintain robustness by enforcing realistic dependency interactions over simulated ones.

How do I check if an ADR violates parent PDR constraints?

You check if an ADR violates parent PDR constraints by evaluating the architectural decision record against established project decision records. This verifies compliance with project-specific constraints and flags misalignments in dependency levels or design principles.

Can I use this code review process for Python microservices architecture?

Yes, this code review process works for Python microservices architecture. It evaluates microservice ADRs to detect incorrect dependency level assignments and improper mocking of external services, ensuring the design adheres to robust testing principles.

What are common mocking prohibitions when reviewing Python architecture?

Common mocking prohibitions when reviewing Python architecture include proposing mocks for external services in ADRs. The review identifies these violations against the /testing methodology, ensuring the architecture relies on real interactions for robustness and maintainability.