validate-audit-benchmarks

You can audit hooks, skills, and commands by running an automated benchmarking suite that scores structural integrity and functional correctness against a predefined rubric, producing an A-F grade to verify release readiness.

Detecting regressions in ValidationForge primitives involves comparing current benchmark scores against an established baseline, highlighting functional or structural deviations in hooks, skills, and commands.

During a benchmark audit, the scoring rubric applies specific weights to each primitive: hooks account for 60%, skills for 20%, and commands for 20% of the total score.

Yes, the benchmarking process produces an A-F grade alongside actionable insights, directly translating the structural and functional scores into readiness assessments for release gates.

You need to establish a baseline for primitive validation during audits, before releases, or immediately after code changes to accurately compare future benchmark scores and identify regressions.

Your pre-release validation grade may drop because hooks carry the highest weight at 60% of the benchmark score, meaning structural or functional regressions in hooks heavily impact the overall A-F grade.