agentsclimarketplace
Sign in

Testability and automation architecture evaluator

Skill anyulled/architecture-guardrails-skills/skills/testability-and-automation-architecture-evaluator

Evaluate test suite architecture for brittle coupling to implementation details, shared state, and poor seam alignment. Use when reviewing tests, mocking strategies, or integration test isolation.From its SKILL.md

Install
npx -y skills add anyulled/architecture-guardrails-skills --skill testability-and-automation-architecture-evaluator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 449 tokens by cl100k_base, as published. Nobody here has run it

Testability and Automation Architecture Evaluator

Analyze test architecture for isolation, seam quality, and implementation coupling.

When to Use

  • PRs that add or refactor tests
  • Periodic test-suite health audits
  • Changes to mocking, fixtures, or integration setup

Scope

  • Scans: test suite source files, mocking frameworks, dependency injection setup, and setup/teardown code that reveal architectural seams in tests.
  • Exclusions: pure helper functions within the same file, generated fixtures, and coverage percentage alone without structural evidence.
  • Fallback: if a seam or boundary is unclear, use the shared conventions heuristic order and downgrade to warning with low confidence.
  • Routing: defer interface-coupling analysis to Integration Strength and Micro-Coupling Evaluator and domain-boundary mapping to Domain Boundary and Language Integrity Evaluator.

Workflow

  1. Detect implementation-detail coupling.
    • Flag tests that target private methods, internals, or reflection-heavy hacks.
    • Prefer assertions through public APIs and architectural boundaries.
  2. Analyze state isolation.
    • Flag shared databases, global mutable state, and missing rollback or container isolation.
    • Detect temporal coupling between tests.
  3. Check seam alignment.
    • Verify mocks and stubs match real boundaries such as HTTP clients, repositories, or adapters.
    • Flag mocking of the subject under test or other invalid test doubles.
  4. Report findings.
    • Return file paths and line numbers for severe coupling.
    • Format output for CI/CD or review bots.

Rules

  • Use static analysis only.
  • Do not evaluate coverage percentages.
  • Focus on architectural test structure, not line-by-line style.

Shared Conventions

  • Follow the repository-wide conventions in shared-skill-conventions.
  • Use the canonical output contract, severity levels, confidence rubric, routing rules, and false-positive downgrades defined there.
  • If this skill is not the closest match, defer to the routing guidance in the shared conventions file.

Output

Return:

  • Implementation-detail coupling findings
  • Shared-state or temporal-coupling risks
  • Seam and stub mismatches
  • CI-ready pass or fail output

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.