Verification Loop

affaan-m/ECC/.kiro/skills/verification-loop

作者 affaan-mef648e01899ba3e8dc6371642deaaf64b4477775無授權條款275K 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫4 天前更新

A comprehensive verification system for Kiro sessions.

AI 產生的概覽

對程式碼庫執行多階段驗證:建置、型別、程式碼檢查、測試、安全掃描與差異審查。

功能
此技能為編碼工作階段定義了一套六階段驗證循環:建置驗證、型別檢查、程式碼檢查、執行含覆蓋率的測試套件、針對金鑰與多餘 console.log 的安全掃描,以及變更檔案的差異審查。它提供 JavaScript/TypeScript 與 Python 專案的 shell 指令,並規定固定的驗證報告格式,涵蓋建置、型別、程式碼檢查、測試、安全與差異,最後給出針對拉取請求的 READY/NOT READY 總體結論。它也描述了持續模式,也就是每 15 分鐘或在重大變更後重複驗證。
適用情境
適用於完成功能或重大程式碼變更之後、建立拉取請求之前、重構之後,或需要讓品質關卡通過時。也適用於長時間工作階段中需要定期重複驗證的情況。
執行需求
僅為說明性指令,不隨附指令碼。需要代理能在專案中執行 shell 指令,並具備建置工具(npm 或 pnpm)、型別檢查器(tsc 或 pyright)、程式碼檢查工具(npm lint 或 ruff)、含覆蓋率的測試執行器、git 與 grep。

Verification Loop Skill

A comprehensive verification system for Kiro sessions.

When to Use

Invoke this skill:

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

Verification Phases

Phase 1: Build Verification

bash
# Check if project buildsnpm run build 2>&1 | tail -20# ORpnpm build 2>&1 | tail -20

If build fails, STOP and fix before continuing.

Phase 2: Type Check

bash
# TypeScript projectsnpx tsc --noEmit 2>&1 | head -30
# Python projectspyright . 2>&1 | head -30

Report all type errors. Fix critical ones before continuing.

Phase 3: Lint Check

bash
# JavaScript/TypeScriptnpm run lint 2>&1 | head -30
# Pythonruff check . 2>&1 | head -30

Phase 4: Test Suite

bash
# Run tests with coveragenpm run test -- --coverage 2>&1 | tail -50
# Check coverage threshold# Target: 80% minimum

Report:

  • Total tests: X
  • Passed: X
  • Failed: X
  • Coverage: X%

Phase 5: Security Scan

bash
# Check for secretsgrep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
# Check for console.loggrep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10

Phase 6: Diff Review

bash
# Show what changedgit diff --statgit 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 verification report:

VERIFICATION REPORT==================
Build:     [PASS/FAIL]Types:     [PASS/FAIL] (X errors)Lint:      [PASS/FAIL] (X warnings)Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)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 every 15 minutes or after major changes:

markdown
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 review.

來源與署名

來源:affaan-m/ECC位於.kiro/skills/verification-loop提交ef648e0

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架