From d0825055c9221e63917bab5cd7380a007ac40a54 Mon Sep 17 00:00:00 2001
From: Andrew <47818697+Nyeriah@users.noreply.github.com>
Date: Thu, 10 Sep 2026 22:56:02 -0300
Subject: [PATCH] docs(agents): state the PR title convention inline (#27568)

---
 .agents/docs/code-review.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.agents/docs/code-review.md b/.agents/docs/code-review.md
index fe7e63689c..70b06beadc 100644
--- a/.agents/docs/code-review.md
+++ b/.agents/docs/code-review.md
@@ -14,7 +14,9 @@ line, not as background reading.
 - Review codestyle on every changed line, even when style is not the change's subject. Run both
   linters and report violations as findings: `python apps/codestyle/codestyle-cpp.py` and
   `python apps/codestyle/codestyle-sql.py`.
-- Title and description follow the [commit message guidelines](https://www.azerothcore.org/wiki/commit-message-guidelines).
+- Title and description follow the [commit message guidelines](https://www.azerothcore.org/wiki/commit-message-guidelines):
+  the title says what the change does, in the imperative (`Correct X loot`); the symptom belongs in
+  the description, not the title.
 - Prefer data over code: when a C++ or script change is also achievable through world DB data
   (SmartAI, conditions, templates), flag the DB-only alternative (see `cpp-scripts.md`).
 - Never take a claim as fact, neither the PR description's nor a comment's. Verify game-data