Verification & Quality Assurance

Verifies code quality with truth scoring and automatic rollback of failed changes.

Updated May 8, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/d-chambaud --skill verification-quality-assurance-frekimanagarm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Verification & Quality Assurance
Source: https://github.com/FrekiManagarm/d-chambaud/tree/main/.agents/skills/verification-quality
Command: npx skills add https://github.com/FrekiManagarm/d-chambaud --skill verification-quality-assurance-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes and agent outputs can silently introduce defects, security issues, or quality regressions. This Skill provides automated verification with quantifiable truth scores and instant rollback so low-quality changes never persist in your codebase. ## Core Features & Use Cases - Truth Scoring: Computes reliability metrics on a 0.0-1.0 scale for files, tasks, and agents, with trends, statistics, and multiple export formats (table, JSON, CSV, HTML). - Verification Checks: Validates code correctness, security, performance, documentation, and best practices against a configurable threshold (default 0.95), with auto-fix and batch modes. - Automatic Rollback: Reverts failed changes via Git in under a second, with selective, dry-run, and backup-first options. - Use Case: In a CI/CD pipeline, run a verification check that outputs JSON, fail the build if the overall score drops below 0.95, and automatically roll back the offending commit. ## Quick Start Run a verification check on my current project and show me the truth scores for any files below the 0.95 threshold.

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 a quality threshold?▼

Run npx Codex-flow@alpha verify check to verify the current directory, or pass --file or --directory to target specific paths. Use --threshold to set the minimum truth score, such as 0.98 for stricter validation.

How do I roll back code changes that failed verification?▼

Use npx Codex-flow@alpha verify rollback --last-good to revert to the last known good state via Git. Options include --selective to roll back only failed files, --dry-run to preview, and --backup-first to create a backup before reverting.

Can verification checks run in GitHub Actions or GitLab CI?▼

Yes, verification outputs structured JSON via --json that CI pipelines can parse. The documentation includes GitHub Actions and GitLab CI examples that fail the build when the overall truth score falls below 0.95.

What does the truth score measure and what is a good value?▼

Truth scores range from 0.0 to 1.0 and reflect code correctness, security, performance, documentation, and best practices. Scores of 0.95-1.0 are production-ready, 0.85-0.94 acceptable, and below 0.75 require immediate action.

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

Large directory scans can exceed default timeouts. Increase the limit with --timeout 60s or split the work using verify batch with --batch-size to process files in smaller groups.