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 从公开仓库中收录这些内容。

举报或申请下架