Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

verification-loop

Étoiles2

Forks2

Mis à jour12 mars 2026 à 11:01

CDD (Compile-Driven Development) verification system. No tests — compile + LSP is the sole truth.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

zhmxiaowo

zhmxiaowo/opencode-simple

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	verification-loop
description	CDD (Compile-Driven Development) verification system. No tests — compile + LSP is the sole truth.
compatibility	opencode
metadata	{"origin":"ECC-CDD"}

CDD Verification Loop Skill

A compile-driven verification system. 不运行任何测试。唯一的验证标准是编译通过 + LSP 无 Error。

When to Use

Invoke this skill:

After completing a feature or significant code change
Before creating a PR
When you want to ensure compile gates pass
After refactoring

Verification Phases

Phase 1: Build / Compile Verification

自动检测项目类型并运行对应命令：

# TypeScript/Node.js
npx tsc --noEmit --pretty 2>&1 | head -30
# OR npm run build / pnpm build

# C# / Unity
dotnet build --no-restore 2>&1 | tail -20

# C++ / Unreal / CMake
cmake --build build/ 2>&1 | tail -20

# Rust
cargo check 2>&1 | tail -20

# Go
go build ./... 2>&1 | tail -20

# Python (type check)
pyright . 2>&1 | head -30

If build fails:

STOP — do not proceed
Invoke sequential-thinking for root cause analysis
Use build-error-resolver agent to fix
Re-run compile until Exit Code 0

Phase 2: LSP Diagnostics Check

Use mcp-language-server to verify:

0 Error-level diagnostics
Review Warning-level diagnostics (optional fix)

Phase 3: Lint Check

# JavaScript/TypeScript
npm run lint 2>&1 | head -30

# Python
ruff check . 2>&1 | head -30

Phase 4: Security Scan

# Check for secrets
grep -rn "sk-" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10

# Check for debug logging
grep -rn "console.log\|Debug.Log\|UE_LOG" src/ 2>/dev/null | head -10

Phase 5: Diff Review

# Show what changed
git diff --stat
git diff HEAD~1 --name-only

Review each changed file for:

Unintended changes
Missing error handling
Potential edge cases

Output Format

After running all phases, produce a CDD verification report:

CDD VERIFICATION REPORT
=======================

Compile:   [PASS/FAIL] (Exit Code: X)
Types/LSP: [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Issues to Fix:
1. ...
2. ...

Continuous Mode

For long sessions, run verification after major changes:

Set a mental checkpoint:
- After completing each function
- After finishing a component
- Before moving to next task

Run: /verify

Integration with Hooks

This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive CDD review.

Plus depuis ce dépôt

même dépôt

agentic-engineering

zhmxiaowo/opencode-simple

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

2026-03-122

ai-first-engineering

zhmxiaowo/opencode-simple

Engineering operating model for teams where AI agents generate a large share of implementation output.

2026-03-122

api-design

zhmxiaowo/opencode-simple

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

2026-03-122

autonomous-loops

zhmxiaowo/opencode-simple

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.

2026-03-122

backend-patterns

zhmxiaowo/opencode-simple

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

2026-03-122

blueprint

zhmxiaowo/opencode-simple

Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

2026-03-122

name	verification-loop
description	CDD (Compile-Driven Development) verification system. No tests — compile + LSP is the sole truth.
compatibility	opencode
metadata	{"origin":"ECC-CDD"}

CDD Verification Loop Skill

A compile-driven verification system. 不运行任何测试。唯一的验证标准是编译通过 + LSP 无 Error。

When to Use

Invoke this skill:

After completing a feature or significant code change
Before creating a PR
When you want to ensure compile gates pass
After refactoring

Verification Phases

Phase 1: Build / Compile Verification

自动检测项目类型并运行对应命令：

# TypeScript/Node.js
npx tsc --noEmit --pretty 2>&1 | head -30
# OR npm run build / pnpm build

# C# / Unity
dotnet build --no-restore 2>&1 | tail -20

# C++ / Unreal / CMake
cmake --build build/ 2>&1 | tail -20

# Rust
cargo check 2>&1 | tail -20

# Go
go build ./... 2>&1 | tail -20

# Python (type check)
pyright . 2>&1 | head -30

If build fails:

STOP — do not proceed
Invoke sequential-thinking for root cause analysis
Use build-error-resolver agent to fix
Re-run compile until Exit Code 0

Phase 2: LSP Diagnostics Check

Use mcp-language-server to verify:

0 Error-level diagnostics
Review Warning-level diagnostics (optional fix)

Phase 3: Lint Check

# JavaScript/TypeScript
npm run lint 2>&1 | head -30

# Python
ruff check . 2>&1 | head -30

Phase 4: Security Scan

# Check for secrets
grep -rn "sk-" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" --include="*.cs" . 2>/dev/null | head -10

# Check for debug logging
grep -rn "console.log\|Debug.Log\|UE_LOG" src/ 2>/dev/null | head -10

Phase 5: Diff Review

# Show what changed
git diff --stat
git diff HEAD~1 --name-only

Review each changed file for:

Unintended changes
Missing error handling
Potential edge cases

Output Format

After running all phases, produce a CDD verification report:

CDD VERIFICATION REPORT
=======================

Compile:   [PASS/FAIL] (Exit Code: X)
Types/LSP: [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Issues to Fix:
1. ...
2. ...

Continuous Mode

For long sessions, run verification after major changes:

Set a mental checkpoint:
- After completing each function
- After finishing a component
- Before moving to next task

Run: /verify

Integration with Hooks

This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive CDD review.