qa-architect

Analyze code changes for SOLID principles and clean architecture compliance.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-architect-dev-gios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-architect
Source: https://github.com/dev-gios/agent-teams-qa/tree/main/skills/qa-architect
Command: npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-architect-dev-gios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code adheres to SOLID principles, clean architecture, and project-specific patterns, preventing architectural decay and maintaining code quality.

Core Features & Use Cases

  • SOLID Principle Adherence: Analyzes code for violations of Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.
  • Architecture Compliance: Checks for layer violations, circular dependencies, and naming convention consistency.
  • Adaptive Analysis: Tailors checks to the project's existing paradigm (OOP, functional, etc.) rather than imposing rigid rules.
  • Veto Power: Critical findings can block merges, requiring explicit user acknowledgment.
  • Use Case: Before merging a new feature, the 'qa-architect' skill reviews the changes to ensure they don't introduce tight coupling or violate the established microservices architecture, flagging any deviations.

Quick Start

Use the qa-architect skill to review the staged code changes for architectural quality.

Frequently Asked Questions about qa-architect

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

FAQPage Schema
How do I check code changes for SOLID principle violations before merging?

To check code changes for SOLID principle violations, analyze the staged commits for adherence to Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles before merging.

What is the best way to enforce clean architecture and prevent layer violations in a codebase?

Enforcing clean architecture and preventing layer violations requires analyzing code changes for architectural integrity, including checking for circular dependencies and naming convention consistency. Critical findings can block merges requiring explicit acknowledgment.

Can I use architectural review for functional programming projects, or does it only work for OOP?

Architectural review can be used for functional programming projects because the analysis adapts to the project's existing paradigm. It tailors checks to the established patterns of the project rather than imposing rigid object-oriented rules.

How do I review staged code changes to ensure they don't introduce tight coupling in a microservices architecture?

Reviewing staged code changes for tight coupling in a microservices architecture requires providing context on the project architecture DNA. The analysis flags deviations and architectural violations that compromise established microservices boundaries.

What are the limitations of automated architecture compliance checks during a code review?

Limitations of automated architecture compliance checks include the requirement for explicit context regarding project architecture DNA and dismissed patterns. Without this context, the analysis cannot target specific architectural deviations effectively.