docs(workflow): enforce PR body accuracy checks

Author: josecelano

.github/agents/github-operator.agent.md

@@ -39,9 +39,10 @@ Do not jump directly to raw API calls if a dedicated MCP or CLI command covers t
 2. Read any local specification or context file needed to perform the task correctly.
 3. Load the relevant repository skill when one exists.
 4. Choose the highest-level GitHub interface that can perform the task safely.
-5. Execute the operation with the minimum number of calls needed.
-6. Verify the result by reading the updated GitHub object or returned URL.
-7. Report only the outcome and key identifiers back to the caller.
+5. For PR descriptions, reconcile the proposed body with the actual branch diff and commit list before applying updates.
+6. Execute the operation with the minimum number of calls needed.
+7. Verify the result by reading the updated GitHub object or returned URL.
+8. Report only the outcome and key identifiers back to the caller.
 
 ## Repository Guidance
 
@@ -58,6 +59,7 @@ Do not jump directly to raw API calls if a dedicated MCP or CLI command covers t
 - Do not assume the visible issue number is the same identifier required by a GitHub API.
 - For sub-issue linking, remember that the REST API expects the child issue's internal GitHub ID,
   not its visible issue number.
+- Do not claim PR implementation changes that are not present in the current HEAD diff.
 - Do not mix GitHub task execution with unrelated code changes.
 - If a PR review comment requires code changes, stop after identifying the actionable request and
   hand control back to the caller or a code-focused agent.
@@ -70,3 +72,4 @@ When finishing a task, return:
 1. What was changed or verified
 2. The key GitHub identifiers or URLs
 3. Any blockers, permissions issues, or follow-up needed
+4. For PR body updates, a short evidence line showing the checked commit range and changed files

.github/skills/dev/git-workflow/open-pull-request/SKILL.md

@@ -22,6 +22,8 @@ Before opening a PR:
 - [ ] Branch is pushed to your fork remote
 - [ ] Commits are GPG signed (`git log --show-signature -n 1`)
 - [ ] All pre-commit checks passed (`linter all`, `cargo machete`, tests)
+- [ ] PR body claims are aligned with the actual commit range (`origin/develop..HEAD`)
+- [ ] If manual verification used temporary local-only patches, PR body explicitly says they are not included
 
 > Important: always open the PR in the **upstream repository**, not in your fork.
 > Resolve upstream from `Cargo.toml` (`repository = "https://github.com/torrust/torrust-tracker"`) and use that value for `gh pr create --repo ...`.
@@ -42,6 +44,11 @@ PR body must include:
 - Validation performed
 - Issue link (`Closes #<issue-number>`)
 
+PR body must not include:
+
+- Claims about code changes that are not present in the branch diff
+- Ambiguous wording that mixes temporary local verification patches with committed implementation
+
 ## Option A (Preferred): GitHub CLI
 
 ```bash
@@ -76,6 +83,15 @@ When MCP pull request management tools are available, create the PR with:
 - [ ] Head branch is correct
 - [ ] CI workflows started
 - [ ] Issue linked in description
+- [ ] PR body still matches branch diff and commit history after final rebases/edits
+
+Quick body-accuracy verification:
+
+```bash
+gh pr view <pr-number> --repo <upstream-owner>/<upstream-repo> --json body
+git diff --name-only origin/develop...HEAD
+git log --oneline origin/develop..HEAD
+```
 
 ## Troubleshooting