Rectification Execution (gatekeeper-fix)

Version number = Current Git branch name; Rules for traceability/attribution/permissions can be found in the

gatekeeper

skill (Sections 2 and 3).

Procedure

1. Locate Pending Rectification Issues

• Read only the lines with [Status = Pending Rectification] and the latest round in

  project root/.gatekeeper/${version number}/review.md

  /

  test.md

  ; if none → prompt to proceed to

  /gatekeeper-next

  and stop.

2. Check Attribution Before Staging

• 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. 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. Fill Back Results with Traceability (Only Two Columns)

• 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. Output Fix List and Prompt Manual Review

• Output issue number + processing result + whether apidoc is synchronized; do not judge completion on your own or advance stages.

Pitfalls

1. Prohibit rectification without basis/beyond scope, and privately clearing issue records.
2. Only fill back the two columns; do not touch other columns in review/test or requirement/progress.