verification-loop

Verify code builds and LSP health across multiple languages without tests.

2|2|Updated Mar 12, 2026

Search Tags:#lsp #static-analysis #compile #lint #diff-review #security-scan #build-verification

Ready to run

npx skills add https://github.com/zhmxiaowo/opencode-simple --skill verification-loop-zhmxiaowo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/zhmxiaowo/opencode-simple/tree/main/.opencode/skills/verification-loop
Command: npx skills add https://github.com/zhmxiaowo/opencode-simple --skill verification-loop-zhmxiaowo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This compile-first verification loop enforces code correctness by requiring a successful build and zero LSP errors, without running tests.

Core Features & Use Cases

Phase-driven verification including Build Verification, LSP Diagnostics, Lint, Security Scan, and Diff Review to prepare code for PRs.
Continuous readiness checks after feature completion or refactoring to catch issues early.
Integrates with existing CI workflows to provide a comprehensive, test-free verification.

Quick Start

Run the verification loop on your project to generate a CDD verification report.

Frequently Asked Questions about verification-loop

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

FAQPage Schema

How do I verify code builds and check LSP health without running tests?▼

To verify code builds and check LSP health without tests, use a compile-first verification loop. It enforces code correctness through phases for build verification, LSP diagnostics, lint, security scans, and diff reviews to determine PR readiness.

What is the best way to check code readiness before creating a pull request?▼

The best way to check code readiness before a PR is a phase-driven verification loop. It evaluates build success, LSP diagnostics, linting, security scans, and diffs to provide a final readiness verdict without executing tests.

Does this build verification loop work with TypeScript, Rust, and Python projects?▼

Yes, this build verification loop works across TypeScript, Rust, Python, C#, C++, and Go projects. It applies phase-driven checks including LSP diagnostics and security scans to ensure code health during feature development or refactoring.

Can I use LSP diagnostics to catch errors after refactoring my codebase?▼

You can use LSP diagnostics to catch errors after refactoring by running a compile-first verification loop. It requires zero LSP errors and successful builds to validate code health continuously after structural changes.

How do I run static analysis and security scans without executing tests?▼

To run static analysis and security scans without tests, execute a verification loop. It implements dedicated phases for lint, security scanning, and diff review, enforcing code correctness purely through compilation and LSP health checks.