Menü
Verify final tests with hard quality gates: integrity, consistency, validator, limit semantics, and wrong-solution kill.
| name | testdata-quality |
| description | Verify final tests with hard quality gates: integrity, consistency, validator, limit semantics, and wrong-solution kill. |
| disable-model-invocation | false |
Final test data must pass:
problem_verify_tests checks: file_count / answer_consistency / validator / no_empty.limit_ratio and limit_semantics (type=3 and type=4 must not be semantically overlapping).wrong_solution_kill: every wrong solution must be killed by at least one test.decision: go / no_gofailed_checks: list of failed checks (with reasons)coverage_report: scale distribution, limit-case ratio, and wrong-solution kill statisticsrepair_priority: fix priority (P0 / P1 / P2)reverify_plan: re-validation order after fixesgo: all required checks pass, limit semantics are valid, and wrong-solution kill is effective.no_go: any required check fails or coverage quality is insufficient.Define and enforce project-wide quality standards for agent and skill documents. Use when creating, reviewing, or refactoring files under agents/ and skills/ to keep structure, terminology, and output contracts consistent.
Validate statement samples and sample files for competitive programming problems. Ensures the expected outputs in problem statements match the actual solution output.
Audit std/brute assumptions with MCP evidence, including worst/average complexity risk and stress readiness.
Audit statement, tutorial, and samples for consistency and publication readiness before packaging.
Build multi-profile stress tests from brute complexity and constraints, then execute with traceable evidence.
Use before coding to decide whether a problem idea is judgeable, implementable, and verifiable.