verification-loop
A multi-stage verification framework for architectural and module changes to ensure system integrity.
Install
mkdir -p .claude/skills/verification-loop-patrick-rex && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15315" && unzip -o skill.zip -d .claude/skills/verification-loop-patrick-rex && rm skill.zipInstalls to .claude/skills/verification-loop-patrick-rex
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Stratum 变更验证闭环技能。用于在提交前对受影响模块、架构边界、文档同步与安全基线做一次可执行检查。Key capabilities
- →Perform narrow-scope builds of affected modules
- →Execute narrow-scope tests to validate changes
- →Conduct architecture redline checks
- →Verify interface and security aspects
- →Ensure documentation synchronization
- →Review final diff for unintended changes
How it works
The skill executes a multi-stage verification pipeline, starting with narrow-scope builds and tests, followed by architecture, interface, security, and documentation checks, concluding with a diff review.
Inputs & outputs
When to use verification-loop
- →Verifying PR changes
- →Ensuring architectural compliance
- →Syncing documentation with code
About this skill
Stratum 验证闭环技能
何时启用
- 完成一个功能或缺陷修复后
- 提交 PR 或准备
git commit前 - 对分层边界、接口契约、安全链路有改动时
- 长会话中每完成一个可验证子目标后
验证阶段
阶段 1：窄范围构建
- 只构建受影响模块，避免一开始跑全仓。
- 示例：
gradlew :stratum-common:buildgradlew :stratum-domain:buildgradlew :stratum-interface:build :stratum-query:build
阶段 2：窄范围测试
- 先跑最能否定当前假设的测试，再扩大范围。
- 示例：
gradlew :stratum-application:testgradlew :stratum-starter:test
阶段 3：架构红线检查
- Domain 不得出现 Spring、EasyQuery、Redis、RabbitMQ 导入或注解。
- Query 不得包含写操作。
- Job 不得直接操作数据库。
- 如需文本检查，可用：
rg "@Transactional|@Service|@Repository|EasyQuery|Redis|RabbitMQ" stratum-domain/src/main/javarg "INSERT|UPDATE|DELETE" stratum-query/src/main/java
阶段 4：接口与安全检查
- 接口改动时检查统一响应、traceId、错误码语义、OpenAPI 注解。
- 安全改动时检查
401/403、敏感日志、密钥来源、RBAC 与数据范围。
阶段 5：文档同步检查
- 若本次会话改动了仓库根目录普通文件，或顶层非点目录下的代码、构建脚本、配置文件，就必须同步更新
docs/CONTEXT.md与docs/entropy/SESSION-HANDOFF.md。 - 若本次会话仅改动顶层点目录（如
.github/、.vscode/）下的文件，可不强制同步上述双文档。 - 若未更新，这次变更直接判定为未完成。
阶段 6：Diff 复核
- 最后再看变更集合，确认没有误改、漏改与多余文件。
输出模板
使用以下格式汇总：
VERIFICATION REPORT
Build: PASS/FAIL
Tests: PASS/FAIL
Architecture: PASS/FAIL
Security: PASS/FAIL
Docs Sync: PASS/FAIL
Overall: READY/NOT READY
Issues:
1. ...
常见反例
- 编辑结束后直接看 diff，不跑任何窄范围校验。
- 全仓命令失败后继续堆改动，失去定位能力。
- 已改代码却漏更
CONTEXT或SESSION-HANDOFF。 - 明知越过架构红线，仍以“后面再改”收尾。
When not to use it
- →When the user wants to look at diff directly without any narrow-scope validation
- →When the user wants to continue making changes after a full command failure
- →When the user wants to ignore architecture redlines
Limitations
- →Domain modules must not import Spring, EasyQuery, Redis, or RabbitMQ.
- →Query modules must not contain write operations.
- →Job modules must not directly operate on databases.
How it compares
This skill provides a structured, executable verification loop that systematically checks various aspects of a change before submission, offering a more complete validation than ad-hoc testing or direct diff review.
Compared to similar skills
verification-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verification-loop (this skill) | 0 | 2mo | No flags | Advanced |
| springboot-verification | 4 | 4mo | Review | Intermediate |
| semoss-testing-ci | 0 | 2mo | No flags | Intermediate |
| ci-loop | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
springboot-verification
affaan-m
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
semoss-testing-ci
SEMOSS
Use when the user wants to add JUnit/Mockito tests for Java reactors, set up pre-commit hooks (husky + the pre-commit framework), or wire GitHub Actions CI (lint + unit-test workflows) to a SEMOSS app. The base template ships none of this to stay lean — this skill carries the full, working setup as
ci-loop
hyodotdev
Run the full CI pipeline locally and iterate until all tests pass.
hexagonal-architecture
jssmy
Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services. Use for: new features needing long-term maintainability, decoupling domain logic from frameworks/DB/HTTP,
mvnf
eclipse-rdf4j
Run Maven tests in this repo with a consistent workflow (module test-artifact cleanup, root -Pquick install to refresh .m2_repo, then module verify or a single test class/method). Use when asked to run tests/verify in the rdf4j multi-module build or when the user says mvnf.
workflow-orchestration-patterns
wshobson
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.