validator-role-skill

Code quality validation automates testing, linting, and security scanning within CI/CD workflows. Run comprehensive test suites, analyze coverage, execute security audits, and generate structured review feedback to catch issues before merge, ensuring PRs meet all quality gates.

Test-driven development starts by creating detailed test plans and writing failing tests before implementation. This approach guides your builder by defining expected behavior upfront, then validates that your implementation satisfies all test cases and maintains required coverage.

Yes. Full test suite execution runs unit, integration, and end-to-end tests in sequence, then analyzes coverage across all test types. Combined with linting and security scans, you get comprehensive validation artifacts showing which code paths are tested and where gaps exist.

Structured code review combines inline feedback categorizing issues by severity, highlights code strengths, and performs security audits to identify vulnerabilities. The result is a detailed report with actionable recommendations and validation artifacts for handoff before merge.

Yes. This validation approach integrates directly into modern CI/CD workflows for pull request validation, test plan creation, and security reviews. It produces comprehensive TEST_PLAN.md and validation artifacts designed for handoff and automated quality gates.

Validation effectiveness depends on existing test coverage, code structure, and linting rule configuration. Large test suites may require performance tuning; legacy code without baseline tests may need incremental test plan creation before full validation can identify comprehensive security or quality gaps.