Verification & Quality Assurance FAQs

Question 1

What is a Truth Score in this skill?

Accepted Answer

A Truth Score is a statistical metric ranging from 0.0 to 1.0 that evaluates the reliability, correctness, and security of code outputs or agent tasks based on predefined quality criteria.

Question 2

What specific aspects of code does the verification system check?

Accepted Answer

The system evaluates five core pillars: Code Correctness (syntax/logic), Best Practices (style/modularity), Security (vulnerabilities/secrets), Performance (complexity/memory), and Documentation accuracy.

Question 3

Can I integrate this skill into my existing CI/CD pipeline?

Accepted Answer

Yes, the skill is designed for integration. It can export structured data in JSON or HTML formats, allowing you to fail builds or generate quality reports automatically in GitHub Actions, GitLab CI, and other platforms.

Question 4

Is the 0.95 threshold adjustable?

Accepted Answer

Absolutely. You can customize the strictness of the verification system using the --threshold flag in the CLI or by updating the configuration file to match your project's specific quality requirements.

Question 5

How does the automatic rollback feature work?

Accepted Answer

If a verification check falls below the defined threshold (default 0.95), the skill uses Git integration to instantly revert the codebase to the last known 'good' state, preventing broken code from persisting.

Verification & Quality Assurance

Verification & Quality Assurance

Key Features

Use Cases

Key Features

Use Cases