Verification & Quality Assurance

Verify code quality with truth scoring, automated checks, and git-based rollback.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/pjherron/hypoc --skill verification-quality-assurance-pjherron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Verification & Quality Assurance
Source: https://github.com/pjherron/hypoc/tree/main/hypoc/skills/verification-quality
Command: npx skills add https://github.com/pjherron/hypoc --skill verification-quality-assurance-pjherron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude-flow.

What problem does it solve? Agent-generated code and task outputs often ship without objective quality gates, letting low-quality or insecure changes persist in the codebase. This skill enforces measurable quality standards through truth scoring, automated verification checks, and instant rollback of changes that fall below a configurable threshold. ## Core Features & Use Cases - Truth Scoring: Computes 0.0-1.0 reliability metrics for code, agents, and tasks with trends, statistics, and exportable reports in JSON, CSV, HTML, or Markdown. - Verification Checks: Validates code correctness, security, performance, documentation, and best practices on files, directories, or task outputs, with optional auto-fix. - Automatic Rollback: Reverts failed changes via git in under a second, with selective, interactive, and dry-run modes. - Use Case: A team wiring quality gates into CI/CD runs verification in GitHub Actions, fails the build when the truth score drops below 0.95, and monitors agent performance trends on a live dashboard. ## Quick Start Run a verification check on my src directory with a 0.95 threshold and show me the truth scores for the last 7 days.

Frequently Asked Questions about Verification & Quality Assurance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a code verification check with claude-flow?▼

Run npx claude-flow@alpha verify check to verify the current directory, or pass --file or --directory to target specific paths. Add --threshold to set a custom score requirement and --auto-fix to correct issues automatically.

How do I integrate truth score verification into CI/CD pipelines?▼

Run verify check with --json to produce structured output, then parse the overallScore field with jq and fail the build when it falls below your threshold. Examples for GitHub Actions and GitLab CI are included in the documentation.

What does the truth score threshold mean in verification?▼

The threshold is the minimum 0.0-1.0 quality score required to pass verification, defaulting to 0.95. Scores of 0.95-1.0 are production-ready, 0.85-0.94 acceptable, and below 0.75 critical, with per-environment overrides supported.

Can I rollback changes that fail verification?▼

Yes, run verify rollback --last-good to revert to the last passing state via git in under a second. Selective, interactive, backup-first, and dry-run modes are available, and rollback requires the project to be a git repository.

Why is my verification check timing out on large codebases?▼

Increase the limit with --timeout 60s or split work using verify batch with --batch-size. Typical performance is under 100ms per file and under 5 seconds for a full project scan.