verification-loop

Automated verification loops execute sequential phases—build, type-check, lint, test, and security scans—to confirm code readiness before PR handoff. Running the full verification loop detects defects early across multiple project types and generates a concise diff summary for review.

Automating type checking, linting, and security scans across multiple languages requires project-type detection via common files like pubspec.yaml, go.mod, package.json, or pom.xml. A phase-based verification tool detects the project type and runs the appropriate checks to ensure code quality.

Automated code verification detects project type by locating configuration files such as pubspec.yaml, go.mod, package.json, and pom.xml in the repository. Once detected, it executes phase-based checks—build, lint, type-check, test, and security scan—matching the identified project ecosystem.

End-to-end build verification and security checks support multiple project types by detecting standard files like go.mod for Go and pubspec.yaml for Flutter. The verification process adapts its build, test, type-check, and lint phases to the specific project configuration found.

A full verification loop is needed before merging because passing tests alone do not guarantee type correctness, lint compliance, or build success. Phase-based verification runs security scans and generates diff summaries, catching defects that tests miss and ensuring complete readiness for handoff.