Add pr-review skill and update branch-sync workflow

Adds a comprehensive PR review skill covering: full branch diff
analysis, standards compliance checklist, documentation requirements,
manual validation, comment resolution, and learning capture back to
skills. Also documents the mandatory master-merge step in git-workflow
and updates SKILL.md, README, and github-interaction with references.

Author: DawoudIO

.agents/skills/README.md

@@ -73,6 +73,7 @@ All project-specific skills live in **[`churchcrm/`](./churchcrm/)**. See [`chur
 ### Development Process
 - [Git Workflow](./churchcrm/git-workflow.md)
 - [GitHub Interaction](./churchcrm/github-interaction.md)
+- [PR Review](./churchcrm/pr-review.md)
 - [Development Workflows](./churchcrm/development-workflows.md)
 - [Code Standards](./churchcrm/code-standards.md)
 - [Wiki Documentation](./churchcrm/wiki-documentation.md)
@@ -103,6 +104,7 @@ They are registered in `~/.claude/CLAUDE.md` for automatic discovery.
 
 **Example workflows:**
 
+- **Review a PR**: `pr-review.md` → `code-standards.md` → `security-best-practices.md` → `wiki-documentation.md`
 - **New API endpoint**: `api-development.md` → `service-layer.md` → `slim-4-best-practices.md` → `security-best-practices.md` → `cypress-testing.md` → `git-workflow.md`
 - **Migrate legacy page**: `routing-architecture.md` → `admin-mvc-migration.md` → `frontend-development.md` → `database-operations.md` → `git-workflow.md`
 - **Fix security issue**: `security-best-practices.md` → `authorization-security.md` → `php-best-practices.md` → `git-workflow.md`

.agents/skills/churchcrm/SKILL.md

@@ -86,7 +86,8 @@ Project-specific skills for AI agents and developers working on ChurchCRM. Each
 |-------|------------|
 | [Git Workflow](./git-workflow.md) | Commits, PRs, pre-commit validation |
 | [GitHub Interaction](./github-interaction.md) | Reviews, commits, PR management |
-| [PR Description Guidelines](./pr-description-guidelines.md) | Ensure PR bodies are written in Markdown with required sections (Summary, Changes, Files Changed, Validation, Testing) |
+| [PR Review](./pr-review.md) | Full PR review: fetch changes, validate standards, check docs/wiki, manual testing, address comments, capture learnings |
+| [PR Description Guidelines](../pr-description-guidelines.md) | Ensure PR bodies are written in Markdown with required sections (Summary, Changes, Files Changed, Validation, Testing) |
 | [Development Workflows](./development-workflows.md) | Setup, build, Docker management |
 | [Code Standards](./code-standards.md) | General coding, quality checks, PR reviews |
 | [Wiki Documentation](./wiki-documentation.md) | Complex documentation, admin guides |
@@ -103,3 +104,5 @@ Project-specific skills for AI agents and developers working on ChurchCRM. Each
 - **Add UI text**: `i18n-localization.md` → `frontend-development.md` → `git-workflow.md`
 - **Write release notes**: `release-notes.md` → `github-interaction.md`
 - **Publish a release**: `release-notes.md` → `social-media-release.md` → `github-interaction.md`
+- **Review a PR**: `pr-review.md` → `code-standards.md` → `security-best-practices.md` → `wiki-documentation.md`
+- **Address PR comments**: `pr-review.md` → `github-interaction.md` → `git-workflow.md`

.agents/skills/churchcrm/git-workflow.md

@@ -191,6 +191,28 @@ Fixes #7698
 - **Testing** - How to verify, test commands
 - **Related Issues** - Links to related issues/PRs
 
+### Keeping Branches Up to Date
+
+**Always merge master into a PR branch before reviewing or testing it.** A branch that has diverged from master may have hidden conflicts or stale code that makes the review misleading.
+
+```bash
+git fetch origin
+git checkout <branch-name>
+git merge origin/master   # Bring branch up to date
+
+# If conflicts arise: resolve, stage, commit, push
+git add <resolved-files>
+git commit -m "Merge master into <branch-name> to resolve conflicts"
+git push origin <branch-name>
+```
+
+**Rules:**
+- Resolve conflicts in favour of the PR's intent — do not silently drop changes
+- Push the merge commit back to origin so CI runs against the updated state
+- If you resolve conflicts on someone else's PR, leave a comment explaining what was resolved
+
+---
+
 ### Code Review Checklist
 
 Before marking PR ready for review, ensure:

.agents/skills/churchcrm/github-interaction.md

@@ -2,6 +2,8 @@
 
 Purpose: practical, step-by-step actions for handling reviews, commits, and PRs. This file is an actionable companion to the canonical `git-workflow.md` (policy) and the `gh-cli` skill (commands).
 
+For a **full PR review workflow** (fetching changes, standards checklist, doc updates, manual validation, capturing learnings), see [`pr-review.md`](./pr-review.md).
+
 Quick checklist — Addressing reviews
 - Read comments and ask clarifying questions if needed.
 - Make one focused change per review thread; add tests where applicable.