Pattern Evolution Auditor FAQs

Question 1

What is the 4-Score Model used by this skill?

Accepted Answer

The model measures Compliance (industry standards), Completeness (observability and tests), Quality (SOLID principles), and Implementation (actual production usage) to provide a holistic view of architectural health.

Question 2

Does this skill integrate with project management tools?

Accepted Answer

Yes, it can automatically create [REFACTOR] or [BUG] stories in Linear when architectural health falls below specific SLA thresholds, provided the Linear MCP is available.

Question 3

Can I use it on large, multi-domain repositories?

Accepted Answer

Absolutely. It features a domain-aware scanning mode that performs per-domain audits and then aggregates systemic issues into a cross-domain health report.

Question 4

How does it handle undocumented patterns?

Accepted Answer

It uses adaptive discovery heuristics to scan for class naming conventions, abstract hierarchies, and structural indicators (like factories or builders) to find patterns that haven't been formally documented yet.

Question 5

What is architectural drift detection?

Accepted Answer

Drift detection compares current scores against baseline audits. If quality or compliance drops by more than the defined SLA threshold (e.g., 10 points), the skill flags a breach and can automate remediation tasks.

Pattern Evolution Auditor

Key Features

Use Cases

Pattern Evolution Auditor

Key Features

Use Cases