Back to Details

verify

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Verify

验证

Use this skill when the user wants confidence that a feature, fix, or refactor actually works.
当用户需要确认功能、修复或者重构确实能够正常运行时，使用本Skill。

Goal

目标

Turn vague “it should work” claims into concrete evidence.
将模糊的“它应该能运行”的说法转化为具体的证据。

Workflow

工作流程

  1. Identify the exact behavior that must be proven.
  2. Prefer existing tests first.
  3. If coverage is missing, run the narrowest direct verification commands available.
  4. If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
  5. Report only what was actually verified.
  1. 识别必须被证明的具体行为。
  2. 优先使用已有的测试。
  3. 如果缺少测试覆盖，运行可用的最小范围的直接验证命令。
  4. 如果直接自动化验证不足，描述手动验证步骤并收集具体的可观察证据。
  5. 仅报告实际完成验证的内容。

Verification order

验证顺序

  1. Existing tests
  2. Typecheck / build
  3. Narrow direct command checks
  4. Manual or interactive validation
  1. 已有测试
  2. 类型检查/构建
  3. 小范围直接命令检查
  4. 手动或交互式验证

Rules

规则

  • Do not say a change is complete without evidence.
  • If a check fails, include the failure clearly.
  • If no realistic verification path exists, say that explicitly instead of bluffing.
  • Prefer concise evidence summaries over noisy logs.
  • 没有证据的情况下不要宣称变更已完成。
  • 如果检查失败，清晰说明失败情况。
  • 如果不存在可行的验证路径，明确说明，不要虚张声势。
  • 优先提供简洁的证据总结，而非杂乱的日志。

Output

输出

  • What was verified
  • Which commands/tests were run
  • What passed
  • What failed or remains unverified
  • 已验证的内容
  • 运行了哪些命令/测试
  • 验证通过的内容
  • 验证失败或仍未验证的内容