From 1290e3b222cf3aff8349501f73e6ca0f00615e6f Mon Sep 17 00:00:00 2001
From: thuanle <tl@thuanle.me>
Date: Tue, 28 Apr 2026 00:22:43 +0700
Subject: [PATCH] docs: require Fixes #<issue> in PR body for auto-close

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---
 AGENT.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/AGENT.md b/AGENT.md
index 86c2b9e..03737e1 100644
--- a/AGENT.md
+++ b/AGENT.md
@@ -58,7 +58,8 @@ All work starts from a Gitea issue. Two phases, each with a dedicated role:
    - Create a feature branch from `main`.
    - Implement following the plan (surgical changes only).
    - Run validation: `go test ./...`, `go vet ./...`, `gofmt -l .`.
-   - Create PR referencing the issue.
+   - Create PR with `Fixes #<issue>` in the body so Gitea auto-closes the issue on merge.
+   - After merge, verify the issue is closed. If not (e.g. missing keyword), close it manually with a summary comment.
 6. **Own the PR until merged:**
    - Monitor for review feedback.
    - Fix feedback on the correct branch (checkout or worktree, never edit remote via API).