Back to Details

stabilization-loop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Stabilize the project:
  1. If there are any local changes, then commit the current code to the local Git repository with commit message "Claude".
  2. Make sure that the code compiles and the linter checks pass. If not, then fix those and go to step 1.
  3. Stop the server if it is running.
  4. Start the server, wait until it is completely up and ready.
  5. Run the tests.
  6. If any test fails, then analyze the test errors, try to fix them and go to step 1.
  7. If the server crashes or logs an error, then analyze the crashes or errors, try to fix them and go to step 1.
  8. If you have the 
    consistency-check
    skill, then run that on the project as well.
  9. Start the server, wait until it is completely up and ready.
  10. Run the tests.
  11. If any test or the server fails, then go to step 6.
  12. Stop the server.
  13. Commit the current code.
  14. Tag the latest commit as "works".
  15. Provide a concise report.
Remarks:
  • CRITICAL: NEVER run more than one instance of the server at the same time.
  • CRITICAL: NEVER run more than one instance of the tests at the same time.
  • CRITICAL: REFUSE to use this skill if the code is configured to connect to a production database or system.
  • CRITICAL: NEVER delete or disable any pre-existing tests.
  • This skill is supposed to be used in the Git working copy of the software set up for local development and testing.
  • This skill is optimized for running a server and testing it, but the server may be substituted with any other software.
  • Keep working in the current branch, do not switch between branches.
  • Add logging as needed, but at the debug level, so it can be turned off later.
  • If you add expensive logging, then protect it with a debug-level condition.
  • Stop only when all tests succeed with no server errors or crashes.
  • Cover any newly added server code with tests.
稳定项目：
  1. 如果存在任何本地变更，将当前代码提交到本地Git仓库，commit message为"Claude"。
  2. 确保代码可编译且linter检查通过。如果不满足，修复问题后回到步骤1。
  3. 如果服务器正在运行，停止服务。
  4. 启动服务器，等待其完全启动就绪。
  5. 运行测试。
  6. 如果有任何测试失败，分析测试错误，尝试修复后回到步骤1。
  7. 如果服务器崩溃或记录错误日志，分析崩溃或错误原因，尝试修复后回到步骤1。
  8. 如果你拥有
    consistency-check
    skill，也在项目上运行该技能。
  9. 启动服务器，等待其完全启动就绪。
  10. 运行测试。
  11. 如果有任何测试失败或服务器运行异常，回到步骤6。
  12. 停止服务器。
  13. 提交当前代码。
  14. 给最新的提交打上"works"标签。
  15. 提供一份简洁的报告。
备注：
  • 重要提示：绝对不要同时运行多个服务器实例。
  • 重要提示：绝对不要同时运行多个测试实例。
  • 重要提示：如果代码配置为连接生产环境数据库或系统，拒绝使用该技能。
  • 重要提示：绝对不要删除或禁用任何预先存在的测试。
  • 该技能应在配置为本地开发和测试的软件Git工作副本中使用。
  • 该技能针对服务器运行和测试场景做了优化，但服务器也可替换为任何其他软件。
  • 保持在当前分支工作，不要切换分支。
  • 根据需要添加日志，但请使用debug级别，方便后续可关闭。
  • 如果你添加了开销较高的日志，请用debug级别的条件判断包裹。
  • 只有当所有测试全部通过，且服务器没有错误或崩溃时才停止操作。
  • 为所有新增的服务器代码补充测试覆盖。