test-guidelines

Enforce substantive, boundary-aware assertions in test suites across CI pipelines.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/dzackgarza/ai --skill test-guidelines-dzackgarza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-guidelines
Source: https://github.com/dzackgarza/ai/tree/main/opencode/skills/test-guidelines
Command: npx skills add https://github.com/dzackgarza/ai --skill test-guidelines-dzackgarza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations struggle to ensure their tests prove real, repository-owned behavior rather than surface-level checks. This Skill helps teams elevate testing standards by focusing on substantive assertions, boundary-aware interpretations, and comprehensive audit criteria.

Core Features & Use Cases

  • Substantive assertions: require concrete invariants and nontrivial checks that prove repository-owned behavior rather than surface-level conditions.
  • Boundary/interlock testing: verify correct interpretation and error handling at dependencies and system interfaces.
  • Audit and governance: provide criteria and workflows to enforce test quality gates across CI and PR reviews.
  • Use Case: QA engineers, developers, and architects apply these guidelines to assess and improve test suites.

Quick Start

Run the high-quality testing audit on your repository to enforce substantive, boundary-aware tests.

Frequently Asked Questions about test-guidelines

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

FAQPage Schema
How do I enforce substantive assertions in test suites?

Boundary and interlock testing verifies correct interpretation and error handling at system interfaces and dependencies. You enforce it by applying test governance criteria during CI pipelines and PR reviews to ensure dependency boundaries are properly checked.

What is boundary and interlock testing for CI pipelines?

Boundary and interlock testing verifies correct interpretation and error handling at system interfaces and dependencies. You enforce it by applying test governance criteria during CI pipelines and PR reviews to ensure dependency boundaries are properly checked.

How do I audit test suites for nontrivial checks?

Test governance criteria provide specific workflows and quality gates to enforce test standards across CI and PR reviews. They ensure tests include substantive assertions and boundary-aware checks, elevating overall codebase quality.

What criteria define a high-quality testing audit?

Test governance criteria provide specific workflows and quality gates to enforce test standards across CI and PR reviews. They ensure tests include substantive assertions and boundary-aware checks, elevating overall codebase quality.

Does this testing approach work for QA engineers and architects?

Use this approach when your tests need to prove real repository-owned behavior rather than surface-level checks. Avoid it if your project only requires basic smoke testing without comprehensive boundary-aware interpretations or substantive assertion requirements.

When should I not use boundary-aware test standards?

Use this approach when your tests need to prove real repository-owned behavior rather than surface-level checks. Avoid it if your project only requires basic smoke testing without comprehensive boundary-aware interpretations or substantive assertion requirements.