verification

Run test, build, lint, and typecheck scripts to produce a weighted score and approval decision.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/rom-orlovich/agents-system --skill verification-rom-orlovich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/rom-orlovich/agents-system/tree/main/agent-bot/agent-engine/.claude/skills/verification
Command: npx skills add https://github.com/rom-orlovich/agents-system --skill verification-rom-orlovich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces subjective code reviews by automatically verifying code quality through a standardized set of checks and a transparent score.

Core Features & Use Cases

  • Scripted verification: runs four core checks (tests, builds, lint, type checks) and weighs results to produce a decision metric.
  • CI integration: easily plugs into PR checks and pre-merge pipelines to prevent low-quality changes.
  • Deterministic outcomes: exit codes drive the score, not subjective opinions.

Quick Start

Run the four verification scripts to obtain a weighted score and an approval decision for the current change.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I automate code quality scoring for pull requests?

Automate code quality scoring for pull requests by running four predefined scripts: test.sh, build.sh, lint.sh, and typecheck.sh. The verification process applies predefined weights to each script's exit codes to produce a deterministic weighted final score and an approval decision.

How do I run lint and type checks in CI pipelines before merging?

Run lint and type checks in CI pipelines by executing the typecheck.sh and lint.sh scripts within your pre-merge validation workflow. These scripted checks evaluate code changes and return exit codes that contribute to a standardized quality score.

Can I integrate automated code verification into existing pre-merge checks?

You can integrate automated code verification into existing pre-merge checks by plugging the four verification scripts directly into your CI pipelines. This prevents low-quality changes from merging by relying on deterministic exit codes rather than subjective opinions.

What is the best way to standardize code reviews across tests and builds?

Standardize code reviews across tests and builds by running test.sh and build.sh to generate objective exit codes. The verification process weighs these results to produce a transparent final score, reducing subjective manual reviews and standardizing quality checks.

Does code quality verification require specific test or build scripts?

Code quality verification requires four specific scripts: test.sh, build.sh, lint.sh, and typecheck.sh. These scripts must be executable in your environment to generate the exit codes needed for calculating the weighted final approval decision.