quality_validator

Run the three-phase validation workflow: static analysis with linters and dependency audits, runtime checks for branch coverage above 80% and performance issues, then deliverable compliance for docs, licenses, and changelogs. Results map to a score that determines ship readiness.

Scores of 90-100 are excellent and ready to ship, 80-89 need minor fixes, 70-79 require review, and anything below 70 needs major rework. The scoring table maps each range to a concrete action.

Yes, the design checklist covers WCAG accessibility compliance, responsive behavior, consistent styling, and cross-browser testing. These items are tracked alongside documentation and code results in the validation report.

Quality validation is the final pre-ship gate covering deliverables, compliance, and runtime quality across the whole release. Code review focuses on individual code changes and should happen earlier; the Skill directs code review tasks to a separate code-review skill.

The static analysis phase runs npm audit or pip audit and blocks packages with known vulnerabilities at the pipeline level. It also verifies SAST scan results are clean before the deliverable passes.