Enforce substantive, boundary-aware assertions in test suites across CI pipelines.
npx skills add https://github.com/dzackgarza/ai --skill test-guidelines-dzackgarza
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
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.
Run the high-quality testing audit on your repository to enforce substantive, boundary-aware tests.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
oalansilvaIdentify policy gaps against required controls and generate a prioritized remediation plan.
kynetic-aiEnforce pre-PR quality gates covering acceptance criteria and test quality.
bostonaholicReproduce, isolate, fix, and verify software defects using test-driven methodology.
latestaiagentsDesign test cases and suites using markdown and BDD/Gherkin formats.
