Back to Details

kf-verify-change

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Verify Change

验证变更

Determine whether existing changes solve the task safely and are ready to hand off.
判断现有变更是否能安全地解决任务并可移交。

Workflow

工作流程

  1. Read the requested outcome, repository guidance, current status, changed files, and complete diff before selecting checks.
  2. Inspect actual tooling and risk. Choose targeted tests, type checking, linting, formatting checks, builds, schema or migration validation, compatibility checks, and broader suites only when relevant.
  3. Review the implementation against nearby repository patterns and the task's observable acceptance criteria.
  4. Run the smallest checks that provide meaningful confidence. Inspect complete failures rather than relying only on exit codes.
  5. When modification is authorized, fix problems caused by the changes and rerun affected checks. Do not conceal or relabel failures.
  6. Inspect the final diff and status for unintended files, generated artifacts, unrelated formatting, dead code, dependencies, and compatibility changes.
  7. Report checks run, results, fixes made, checks not run, and remaining risk.
  1. 在选择检查项之前，先阅读预期成果、仓库指南、当前状态、已变更文件以及完整的差异内容。
  2. 检查实际工具和风险。仅在相关时选择针对性测试、类型检查、代码扫描、格式检查、构建、架构或迁移验证、兼容性检查以及更全面的测试套件。
  3. 对照仓库中同类模式和任务的可观察验收标准审查实现方案。
  4. 运行能提供有效信心的最小范围检查。检查完整的失败情况，而非仅依赖退出码。
  5. 当获得修改授权时，修复变更导致的问题并重新运行受影响的检查。不要隐瞒或重新标记失败情况。
  6. 检查最终的差异和状态，查看是否存在意外文件、生成的工件、无关的格式调整、死代码、依赖项以及兼容性变更。
  7. 报告已运行的检查、结果、已修复的问题、未运行的检查以及剩余风险。

Final review questions

最终审查问题

  • Does the change solve the requested task?
  • Does it follow repeated repository patterns?
  • Does it preserve unrelated behavior?
  • Did it introduce unnecessary abstractions or dependencies?
  • Does it touch unrelated code or formatting?
  • Is a simpler complete implementation available?
  • Were the relevant checks actually run?
Verification is evidence, not ceremony. Do not blindly run every expensive check.
  • 该变更是否解决了请求的任务？
  • 它是否遵循仓库中的重复模式？
  • 它是否保留了无关功能的原有行为？
  • 它是否引入了不必要的抽象或依赖项？
  • 它是否涉及无关代码或格式调整？
  • 是否存在更简洁的完整实现方案？
  • 相关的检查是否实际运行了？
验证是提供证据，而非形式主义。不要盲目运行所有成本高昂的检查。