implement

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Before Starting

开始之前

  • [ ] Make sure the user has specified which Github issue for the feature or fix to be implemented. If you do not have a Github issue you cannot proceed and must quit.
  • 确认用户已指定要实现的功能或修复对应的Github issue。如果没有Github issue,你不能继续进行,必须终止操作。

Methodology

方法流程

You strictly follow this methodology when implementing a fix.
Prepare and Plan > Implement feature using TDD > Build & Ship
  1. Prepare and Plan. In this phase, you will prepare for the development of the Fix. For this, you MUST use the
    prepare
    skill.
  2. Implement fix using TDD. In this phase, you will code. You will implement the Fix. For this, you MUST use the
    code
    skill.
  3. Build and Ship. In this phase, you will build and ship the implemented code. For this, you MUST use the
    build-and-ship
    skill.
在实施修复时,你必须严格遵循以下方法流程。
准备与规划 > 使用TDD实现功能 > 构建与发布
  1. 准备与规划。在此阶段,你将为修复的开发工作做准备。为此,你必须使用
    prepare
    技能。
  2. 使用TDD实现修复。在此阶段,你将进行编码,完成修复的实现。为此,你必须使用
    code
    技能。
  3. 构建与发布。在此阶段,你将构建并发布已实现的代码。为此,你必须使用
    build-and-ship
    技能。

Acceptance Criteria

验收标准

  • [ ] You have used the
    prepare
    skill
  • You have used the
    code
    skill
  • You have used the
    build-and-ship
    skill
  • [ ] You have committed the changed code. If you have not done that, you must understand why and make sure you do.
  • [ ] You have pushed the change to the right branch.
  • [ ] You are not done until ALL three phases (prepare → code → build-and-ship) have been executed. Only report to the user after build-and-ship is complete.
  • 你已使用
    prepare
    技能
  • 你已使用
    code
    技能
  • 你已使用
    build-and-ship
    技能
  • 你已提交修改后的代码。如果尚未提交,你必须明确原因并确保完成提交。
  • 你已将修改推送到正确的分支。
  • 只有在完成全部三个阶段(准备→编码→构建与发布)后,才算完成任务。仅在构建与发布完成后向用户汇报。