gatekeeper-fix
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese整改执行(gatekeeper-fix)
Rectification Execution (gatekeeper-fix)
版本编号 = 当前 Git 分支名;留痕/归属/权限规则见skill(第二、三节)。gatekeeper
Version number = Current Git branch name; Rules for traceability/attribution/permissions can be found in theskill (Sections 2 and 3).gatekeeper
Procedure
Procedure
1. 定位待整改问题
1. Locate Pending Rectification Issues
- 只读 /
项目根/.gatekeeper/${版本编号}/review.md中【状态=待整改】行与最新轮次;无 → 提示可进test.md,停止。/gatekeeper-next
- Read only the lines with [Status = Pending Rectification] and the latest round in /
project root/.gatekeeper/${version number}/review.md; if none → prompt to proceed totest.mdand stop./gatekeeper-next
2. staging 先判归属
2. Check Attribution Before Staging
- 处理 test.md 问题前,先 read requirement.md 原文引用对应条目,判「需求已有 → 修复 / 需求未覆盖 → 不修,待人工补需求」。
- Before handling issues in test.md, first read the corresponding entries referenced in requirement.md, then judge: "Requirement exists → Fix / Requirement not covered → Do not fix, wait for manual requirement supplement."
3. 针对性修复
3. Targeted Fixes
- 只改待整改项,不新增功能、不超范围、无依据不整改;误报置「无需整改」附理由。
- Only modify items pending rectification; do not add new features, exceed scope, or rectify without basis. Mark false positives as "No Rectification Needed" with reasons.
4. 回填留痕(仅两列)
4. Fill Back Results with Traceability (Only Two Columns)
- 只改【状态】(待整改→已整改待复核 / 无需整改)与【整改结果】两列;接口契约变化须声明 apidoc 已同步。
- Only modify the [Status] (Pending Rectification → Rectified Pending Review / No Rectification Needed) and [Rectification Result] columns; if interface contract changes, must declare that apidoc has been synchronized.
5. 输出修复清单,提示人工复核
5. Output Fix List and Prompt Manual Review
- 输出问题序号 + 处理结果 + 是否 apidoc 同步;不自行判定完成、不推进阶段。
- Output issue number + processing result + whether apidoc is synchronized; do not judge completion on your own or advance stages.
Pitfalls
Pitfalls
- 禁止无依据/超范围整改、私自清空问题记录。
- 只回填两列,不碰 review/test 其他列或 requirement/progress。
- Prohibit rectification without basis/beyond scope, and privately clearing issue records.
- Only fill back the two columns; do not touch other columns in review/test or requirement/progress.