bd-close-reviewed

To safely close review-gated GitHub issues, you must enforce typechecks, execute the issue's verify line, and obtain path-matched surface reviewer approvals before closure. This prevents premature issue closure by refusing to complete the process until all safety gates pass.

When a typecheck or verify gate fails during issue closure, the system enforces strict refusal behavior and prevents the issue from closing. The issue remains open until the underlying typecheck or verify-line execution passes successfully.

Yes, you can override a BLOCK or FIX_BEFORE_MERGE reviewer result, but only through an explicit, user-confirmed authorization flow. The override is then recorded correctly during the final phase=close invocation to maintain auditability.

Path-matched surface reviewers dispatch only the relevant security or repo-boundary reviewers based on the specific files the diff touches. This targeted fan-out ensures appropriate code review coverage without running unnecessary checks on unaffected paths.

Yes, if an issue has missing or placeholder verify content, the system requires explicit user acknowledgement before proceeding with closure. This ensures the verify-line enforcement gate is not bypassed silently without human confirmation.

Use an automated verify gate when finishing /bd-execute loops or when implementations were performed manually outside that workflow. It ensures typechecks and surface reviews run consistently, preventing unsafe manual closures of story-editor issues.