Ensures code quality through real-time reliability metrics and automated rollback triggers for CI/CD pipelines.
Install
mkdir -p .claude/skills/verification-quality-assurance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6824" && unzip -o skill.zip -d .claude/skills/verification-quality-assurance && rm skill.zipInstalls to .claude/skills/verification-quality-assurance
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.Key capabilities
- →Provide real-time reliability metrics for code, agents, and tasks
- →Validate code correctness, security, and best practices automatically
- →Revert changes that fail verification with a 0.95 threshold
- →Analyze quality with trends, confidence intervals, and improvement tracking
- →Integrate into continuous integration pipelines
- →Monitor verification with live dashboards and watch modes
How it works
The skill provides a system for truth scoring, automated verification checks, and automatic rollback of changes that do not meet a 0.95 accuracy threshold. It integrates with CI/CD pipelines and offers real-time monitoring.
Inputs & outputs
When to use verification-quality-assurance
- →Validate code correctness before deployment
- →Monitor agent output reliability
- →Automate regression testing in CI/CD
- →Perform quality trend analysis
About this skill
Verification & Quality Assurance Skill
What This Skill Does
This skill provides a comprehensive verification and quality assurance system that ensures code quality and correctness through:
- Truth Scoring: Real-time reliability metrics (0.0-1.0 scale) for code, agents, and tasks
- Verification Checks: Automated code correctness, security, and best practices validation
- Automatic Rollback: Instant reversion of changes that fail verification (default threshold: 0.95)
- Quality Metrics: Statistical analysis with trends, confidence intervals, and improvement tracking
- CI/CD Integration: Export capabilities for continuous integration pipelines
- Real-time Monitoring: Live dashboards and watch modes for ongoing verification
Shipped vs. aspirational. The concrete, in-CI verification stack — the 6 regression-guard jobs + the witness manifest + the tool-discoverability audit — is real and runs on every push. The truth-scoring / auto-rollback / WebSocket-dashboard surface described later in this doc is partly shipped (
ruflo verifyruns the witness checks) and partly design — treat the "CI Guards" section below as the authoritative current state.
CI Guards — what's actually shipped (current state)
Ruflo's regression protection is three layers, all gated before publish. Authoritative reference: verification/README.md.
| Layer | What | CI job(s) in .github/workflows/v3-ci.yml | ADR |
|---|---|---|---|
| 1 — install/behavioral smoke | Exercise user-visible failure modes against a real build | smoke-install-no-bsqlite (npm install on platforms w/o prebuilds), plugin-hooks-smoke (#1859/#1862 — hook flag parsing), mcp-protocol-smoke (#1874 — HTTP MCP wire format), memory-import-smoke (#1883/#1884 — WSL path + key sanitization), mcp-roundtrip-smoke (#1889 paired-tool round-trip + #1863 cli-no-crash + ADR-095 G2 consensus-transport) | ADR-102 |
| 1 — discoverability gate | Every MCP tool description must answer "use this over native when?" | tool-descriptions-audit — scripts/audit-tool-descriptions.mjs, baseline at verification/mcp-tool-baseline.json (monotone-decreasing: noGuidance / tooShort / duplicates) | ADR-112 |
| 2 — cryptographic witness | Every documented fix's load-bearing marker must still be present in dist; Ed25519-signed, per-OS bundles | witness-verify (ubuntu/macos/windows) — plugins/ruflo-core/scripts/witness/verify.mjs against verification/<os>/manifest.md.json | ADR-103 |
| 3 — temporal history | When was a regression introduced | verification/<os>/history.jsonl + history.mjs (summary / regressions / timeline) | ADR-103 |
Run the guards locally
# Tool-description discoverability audit (ADR-112)
node scripts/audit-tool-descriptions.mjs # fails if any baseline count rises
node scripts/audit-tool-descriptions.mjs --update-baseline # lock the new floor after a fix lands
# Behavioral smokes (each builds what it needs; safe to run individually)
node plugins/ruflo-core/scripts/test-hooks.mjs "node $PWD/v3/@claude-flow/cli/bin/cli.js"
node plugins/ruflo-core/scripts/test-mcp-protocol.mjs
node plugins/ruflo-core/scripts/test-memory-import.mjs
node plugins/ruflo-core/scripts/test-mcp-roundtrips.mjs # #1889 paired-tool round-trip
node plugins/ruflo-core/scripts/test-cli-no-crash.mjs # #1863 unhandled-exception class
node plugins/ruflo-core/scripts/test-consensus-transport.mjs # ADR-095 G2 consensus transport
# Witness manifest — regenerate + verify
node scripts/regen-witness.mjs
node plugins/ruflo-core/scripts/witness/verify.mjs --manifest verification/macos/manifest.md.json
# Temporal history
node plugins/ruflo-core/scripts/witness/history.mjs --history verification/macos/history.jsonl summary
node plugins/ruflo-core/scripts/witness/history.mjs --history verification/macos/history.jsonl regressions
Adding a new guard
- Behavioral smoke → write
plugins/ruflo-core/scripts/test-<name>.mjs. Pattern: static dist-scan first (fast, always completes), behavioral probe second with an internal timeout + a process-level watchdog so CI never hangs. Add a step to the relevant job inv3-ci.yml. - Static gate with a baseline → write
scripts/audit-<name>.mjsthat scans, counts violations, and fails if the count exceeds a monotone-decreasing baseline inverification/<name>-baseline.json. Support--update-baseline. Add a CI job; wire it intowitness-verifyneeds[]if it should gatepublish. - Documented-fix marker → append
{ id, desc, file, marker }toverification/witness-fixes.json, runnode scripts/regen-witness.mjs. The marker must be a substring the fix specifically creates (not a generic pattern like'function').
Prerequisites
- Ruflo installed (
npx ruflo@alpha) - Git repository (for rollback features)
- Node.js 18+ (for dashboard features)
@noble/ed25519(for the witness verifier — a single runtime dep,npm i @noble/ed25519)
Quick Start
# View current truth scores
npx ruflo@alpha truth
# Run verification check
npx ruflo@alpha verify check
# Verify specific file with custom threshold
npx ruflo@alpha verify check --file src$app.js --threshold 0.98
# Rollback last failed verification
npx ruflo@alpha verify rollback --last-good
Complete Guide
Truth Scoring System
View Truth Metrics
Display comprehensive quality and reliability metrics for your codebase and agent tasks.
Basic Usage:
# View current truth scores (default: table format)
npx ruflo@alpha truth
# View scores for specific time period
npx ruflo@alpha truth --period 7d
# View scores for specific agent
npx ruflo@alpha truth --agent coder --period 24h
# Find files$tasks below threshold
npx ruflo@alpha truth --threshold 0.8
Output Formats:
# Table format (default)
npx ruflo@alpha truth --format table
# JSON for programmatic access
npx ruflo@alpha truth --format json
# CSV for spreadsheet analysis
npx ruflo@alpha truth --format csv
# HTML report with visualizations
npx ruflo@alpha truth --format html --export report.html
Real-time Monitoring:
# Watch mode with live updates
npx ruflo@alpha truth --watch
# Export metrics automatically
npx ruflo@alpha truth --export .claude-flow$metrics$truth-$(date +%Y%m%d).json
Truth Score Dashboard
Example dashboard output:
📊 Truth Metrics Dashboard
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall Truth Score: 0.947 ✅
Trend: ↗️ +2.3% (7d)
Top Performers:
verification-agent 0.982 ⭐
code-analyzer 0.971 ⭐
test-generator 0.958 ✅
Needs Attention:
refactor-agent 0.821 ⚠️
docs-generator 0.794 ⚠️
Recent Tasks:
task-456 0.991 ✅ "Implement auth"
task-455 0.967 ✅ "Add tests"
task-454 0.743 ❌ "Refactor API"
Metrics Explained
Truth Scores (0.0-1.0):
1.0-0.95: Excellent ⭐ (production-ready)0.94-0.85: Good ✅ (acceptable quality)0.84-0.75: Warning ⚠️ (needs attention)<0.75: Critical ❌ (requires immediate action)
Trend Indicators:
- ↗️ Improving (positive trend)
- → Stable (consistent performance)
- ↘️ Declining (quality regression detected)
Statistics:
- Mean Score: Average truth score across all measurements
- Median Score: Middle value (less affected by outliers)
- Standard Deviation: Consistency of scores (lower = more consistent)
- Confidence Interval: Statistical reliability of measurements
Verification Checks
Run Verification
Execute comprehensive verification checks on code, tasks, or agent outputs.
File Verification:
# Verify single file
npx ruflo@alpha verify check --file src$app.js
# Verify directory recursively
npx ruflo@alpha verify check --directory src/
# Verify with auto-fix enabled
npx ruflo@alpha verify check --file src$utils.js --auto-fix
# Verify current working directory
npx ruflo@alpha verify check
Task Verification:
# Verify specific task output
npx ruflo@alpha verify check --task task-123
# Verify with custom threshold
npx ruflo@alpha verify check --task task-456 --threshold 0.99
# Verbose output for debugging
npx ruflo@alpha verify check --task task-789 --verbose
Batch Verification:
# Verify multiple files in parallel
npx ruflo@alpha verify batch --files "*.js" --parallel
# Verify with pattern matching
npx ruflo@alpha verify batch --pattern "src/**/*.ts"
# Integration test suite
npx ruflo@alpha verify integration --test-suite full
Verification Criteria
The verification system evaluates:
-
Code Correctness
- Syntax validation
- Type checking (TypeScript)
- Logic flow analysis
- Error handling completeness
-
Best Practices
- Code style adherence
- SOLID principles
- Design patterns usage
- Modularity and reusability
-
Security
- Vulnerability scanning
- Secret detection
- Input validation
- Authentication$authorization checks
-
Performance
- Algorithmic complexity
- Memory usage patterns
- Database query optimization
- Bundle size impact
-
Documentation
- JSDoc/TypeDoc completeness
- README accuracy
- API documentation
- Code comments quality
JSON Output for CI/CD
# Get structured JSON output
npx ruflo@alpha verify check --json > verification.json
# Example JSON structure:
{
"overallScore": 0.947,
"passed": true,
"threshold": 0.95,
"checks": [
{
"name": "code-correctness",
"score": 0.98,
"passed": true
},
{
"name": "security",
"score": 0.91,
"passed": false,
"issues": [...]
}
]
}
Automatic Rollback
Rollback Failed Changes
Automatically revert changes that fail verification checks.
Basic Rollback:
# Rollback to last known good state
npx ruflo@alpha verify rollback --last-good
# Rollback to sp
---
*Content truncated.*
Prerequisites
Limitations
- →The truth-scoring and auto-rollback features are partly shipped or in design
- →The authoritative current state is defined by the "CI Guards" section
How it compares
This skill automates code quality checks and rollbacks based on a defined accuracy threshold, unlike manual review processes.
Compared to similar skills
verification-quality-assurance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verification-quality-assurance (this skill) | 1 | 3mo | Review | Intermediate |
| verify | 6 | 6mo | No flags | Beginner |
| code-change-verification | 4 | 4mo | Review | Beginner |
| springboot-verification | 4 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
code-change-verification
openai
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
springboot-verification
affaan-m
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
cicd-diagnostics
dotCMS
Diagnoses DotCMS GitHub Actions failures (PR builds, merge queue, nightly, trunk). Analyzes failed tests, root causes, compares runs. Use for "fails in GitHub", "merge queue failure", "PR build failed", "nightly build issue".
moai-workflow-testing
modu-ai
Comprehensive development workflow specialist combining DDD testing, debugging, performance optimization, code review, PR review, and quality assurance into unified development workflows
posthog-ci-integration
jeremylongshore
Configure PostHog CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating PostHog tests into your build process. Trigger with phrases like "posthog CI", "posthog GitHub Actions", "posthog automated tests", "CI posthog".