verification

Name: verification
Author: diegosouzapw

Other Community

Repo stars 39
Author updated Live
Author repo awesome-omni-skill

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Other
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @diegosouzapw · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview verification.preview

---
name: verification
description: Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 |…
category: other
runtime: no special runtime
---

# verification output preview

## PART A: Task fit
- Use case: Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 | 调用方式 | |:---|:---|:---|:---| | Superpowers verification-before-completion | Plugin Skill | 完成前结构化检查 | 自动: V 阶段触发 | | cunzhi MCP | MCP | 验证失败时寸止 | cunzhi.confirm(VERIFY_FAIL) | | skill/debugging | VibeCoding Skill | 2 次失败后加载 | 按需 | runs entirely locally. Works ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “工具 / 流程 / 验证清单 (按 Path 分级)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 | 调用方式 | |:---|:---|:---|:---| | Superpowers verification-before-completion | Plugin Skill | 完成前结构化检查 | 自动: V 阶段触发 | | cunzhi MCP | MCP | 验证失败时寸止 | cunzhi.confirm(VERIFY_FAIL) | | skill/debugging | VibeCoding Skill | 2 次失败后加载 | 按需 | runs entirely locally. Works …”.
- **02** When the source has headings, the agent prioritizes “工具 / 流程 / 验证清单 (按 Path 分级)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: verification
description: Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 |…
category: other
source: diegosouzapw/awesome-omni-skill
---

# verification

## When to use
- Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 | 调用方式 | |:---|:---|:--…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “工具 / 流程 / 验证清单 (按 Path 分级)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "verification" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> 工具 / 流程 / 验证清单 (按 Path 分级)
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Path-conditional verification checklist (basic/standard/strict) with retry loop | 工具 | 类型 | 用法 | 调用方式 | |:---|:---|:---|:---| |…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “工具”, “流程”, “验证清单 (按 Path 分级)”, “Path A — 基础验证”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name verification directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “工具 / 流程 / 验证清单 (按 Path 分级)” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

验证循环

工具

工具	类型	用法	调用方式
Superpowers verification-before-completion	Plugin Skill	完成前结构化检查	自动: V 阶段触发
cunzhi MCP	MCP	验证失败时寸止	`cunzhi.confirm(VERIFY_FAIL)`
skill/debugging	VibeCoding Skill	2 次失败后加载	按需

流程

1. → Superpowers verification-before-completion
2. 执行验证清单 (按 Path 选择)
3. 通过? → done.md (verified: true)
4. 失败?
   → 分析原因 → 修复 → 重试 (max 3)
   → 第 2 次失败: 加载 skill/debugging
   → 第 3 次失败: cunzhi [VERIFY_FAIL] 请求人工

验证清单 (按 Path 分级)

Path A — 基础验证

□ 所有测试通过
□ Lint 通过
□ 无 console.log / debugger 残留

不检查 plan.md (Path A 无 P 阶段)。

Path B — 标准验证

□ 所有测试通过
□ TypeScript 类型检查 (tsc --noEmit)
□ Lint 通过
□ plan.md 目标逐项覆盖
□ 验收标准逐项满足
□ 无 console.log / debugger 残留
□ 无注释掉的代码块

Path C/D — 严格验证

□ Path B 全部清单
□ 覆盖率达标 (C: 80%, D: 85%)
□ 无未使用 import
□ 组件 <200 行
□ 单文件 <500 行
□ 安全检查通过 (无硬编码密钥/未验证输入)

.ai_state

通过 → done.md 标记 verified: true
失败 → todo.md 追加修复子任务

降级

Superpowers 未安装 → 直接执行上述清单 (AI 自主检查)。

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add diegosouzapw/awesome-omni-skill/skills/development/verification -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
diegosouzapw/awesome-omni-skill
中文

More by @diegosouzapw

Category & tags

Category Other