fix: close implements tracker gap and clarify closing keywords (#110)

skills/llm-project-workflow/SKILL.md

@@ -90,8 +90,8 @@ is maintained by:
 - the branch name (contains the issue number),
 - a claim comment on the issue, e.g.
   `Claimed. Branch: fix/issue-123-short-description. Worktree: branches/fix-issue-123-short-description.`,
-- the PR body — `Closes #123` when the PR should close the issue, `Refs #123`
-  when related but not closing,
+- the PR body — `Closes #123` or `Fixes #123` when the PR should close the issue
+  (do NOT use `Implements #123` or `Refs #123` to close, as Gitea will not auto-close),
 - cleanup after merge — remove the remote branch, local branch, and the issue
   worktree folder, and drop `status:in-progress`.
 

skills/llm-project-workflow/templates/merge-pr.md

@@ -19,7 +19,7 @@ Steps:
    - Target task role: merger identity (must NOT be the PR author)
    *If the current identity does not match the required role (or is the PR author), STOP. Relaunch/switch to the correct profile first.*
 2. Verify authenticated identity + active profile.
-3. Confirm PR #<pr>: author (not you), state open, mergeable, review approved.
+3. Confirm PR #<pr>: author (not you), state open, mergeable, review approved. Check if PR body uses `Closes #N` or `Fixes #N`; if it uses `Implements #N` or `Refs #N`, manual closing will be needed in step 29.
 4. If any gate fails → STOP and report.
 4. Merge with explicit confirmation (e.g. confirmation="MERGE PR <pr>"),
    optionally pinning the reviewed head SHA / changed-file set.

skills/llm-project-workflow/templates/review-pr.md

@@ -24,7 +24,7 @@ Steps:
 4. scripts/worktree-review <pr-head-branch>          # detached, branches/review-*
    cd branches/review-<pr-head-branch-slug>
 5. Confirm the worktree is clean. Inspect the FULL diff; confirm scope matches
-   issue #<n>; flag any unrelated files, secrets, or formatting churn.
+   issue #<n>; flag any unrelated files, secrets, or formatting churn. Check that the PR body correctly uses Gitea-closing keywords (`Closes #N` or `Fixes #N`) instead of non-closing ones (`Implements #N`, `Refs #N`).
 6. Run the test suite; note results.
 7. Post the review verdict: approve only if scope is clean and checks pass;
    otherwise request changes with specifics. Never merge from this review step.

skills/llm-project-workflow/templates/start-issue.md

@@ -28,6 +28,7 @@ Steps:
 6. Checks: run the test suite, compile/lint changed files, git diff --check,
    and scan the diff for secrets.
 7. Commit (issue-linked message), push the branch, open a PR to master.
+   *The PR body MUST use closing keywords like `Closes #N` or `Fixes #N` to close the issue; do NOT use `Implements #N` or `Refs #N` for closing, as Gitea will not auto-close it.*
    Include an "LLM Handoff Metadata" block in the PR body (attribution only;
    never an eligibility input — docs/llm-agent-sha.md):