update hash , example and paragraph

Author: Prab-27

AGENTS.md

@@ -172,7 +172,9 @@ Write commit messages focused on user impact, not implementation details.
 
 - **Good:** `Fix airflow dags test command failure without serialized Dags`
 - **Good:** `UI: Fix Grid view not refreshing after task actions`
-- **Bad:** `Initialize Dag bundles in CLI get_dag function(#12345)`
+- **Good:** `Update foo function`
+- **Bad:** `Initialize Dag bundles in CLI get_dag function`
+- **Bad:** `Update foo function (#12345)`
 - **Bad:** `fix(cli): dags test failure` — Airflow does not use Conventional Commits
   (`feat:`, `fix:`, `chore:` …). Write the subject as plain prose. A `commit-msg`
   prek hook (`check-no-conventional-commit-message`) rejects these, and CI checks
@@ -188,7 +190,13 @@ Use the **imperative mood** and a plain message — do **not** use Conventional
 convention. (Area tags the project already uses, like `UI:` / `API:` / `Helm:`, are fine;
 Conventional-Commit `type:` tokens are not.) The same rule applies to PR titles.
 
-Do not include the issue number, a commit hash, or any other tracking identifier in the title (e.g. `(#12345)` or a trailing hash) — reference the issue in the PR **body** instead, using `closes: #ISSUE` or `related: #ISSUE`, so GitHub auto-links it.
+Do not include an issue or PR number in the PR title. GitHub already appends
+the actual PR number automatically when a PR is squash-merged (this is why
+Airflow's git history is full of titles like `... (#71609)`). Manually
+adding a number in the title duplicates that auto-added number, and readers
+cannot tell whether the number in the title refers to an issue or a PR —
+which is misleading in the commit history and changelog. Reference the
+issue only in the PR description, not the title
 
 The commit message **body** should describe **why** the change is made — the motivation and
 context — and **never what** the change is. The diff already shows what changed; restating it in

dev/skill-evals/last-eval-hash.txt

@@ -1,3 +1,3 @@
 # Generated by dev/skill-evals/eval.py — do not edit or resolve conflicts by hand.
 # Run `prek run run-skill-eval --hook-stage manual --all-files` to regenerate.
-8cfe725b810c4c2d364d99f63b27ec739545e40032195624c218b0eb23d75859
+1e22caec87595e573e6281b901cb6a3d2b16a6c82432d5d281bb7f8b6a455d46