Agent skill · operations · daffy0208
Quality Assurance
Comprehensive quality assurance combining testing strategy, code quality enforcement, and validation gates. Consolidated from testing-strategist, code-quality-enforcer, and validation-gate-checker.
Why this skill is useful
Provides a comprehensive testing strategy and code quality enforcement that the AI wouldn't reliably generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2025-12-25. 33 stars on the source repository.
What this skill does
Quality Assurance Overview Quality Assurance is a consolidated skill that combines three critical quality dimensions: comprehensive testing strategy, code quality enforcement, and phase-gate validation. It ensures your code is tested, maintainable, and ready for production at every stage. Consolidated from: testing-strategist - Test pyramid and comprehensive testing code-quality-enforcer - Code standards and best practices validation-gate-checker - Phase transition validation When to Use This Skill Use Quality Assurance when: Setting up testing infrastructure for a project Conducting code reviews Validating readiness to move between project phases Establishing quality standards for a team Debugging quality issues in production Improving code maintainability Ensuring production readiness Key Capabilities Testing Strategy (from testing-strategist) Design test pyramid with optimal coverage Define unit, integration, and E2E test strategies Set coverage targets and quality metrics Choose testing frameworks and tools Plan test automation and CI/CD integration Code Quality (from code-quality-enforcer) Enforce coding standards and best practices Review code for readability and maintainability Identify security vulnerabilities and anti-patterns Ensure type safety and error handling Refactor code to improve quality scores Validation Gates (from validation-gate-checker) Define phase transition criteria Validate readiness for next phase Ensure deliverables are complete Check compliance with standards Prevent premature phase transitions Workflow Part 1: Testing Strategy The Test Pyramid Structure: Rationale: Unit tests are fast, isolated, cheap to maintain Integration tests catch component interaction issues E2E tests validate critical user workflows, but are slow and brittle --- Unit Tests (70% of tests) Coverage Targets: Critical code (auth, payments, security): 100% Business logic: >90% Overall codebase: >85% What to Test: Pure functions and business logic Edge cases and erro …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daffy0208/quality-assurance