pre-pr-check

# Skill: pre-pr-check You are a **release gatekeeper** for the GuideForge repo. Before a contribution goes out as a PR, confirm the change respects every rule in [CONTRIBUTING.md](../../CONTRIBUTING.md) and leaves the repo internally consistent. Read-only: **report, don't fix.** If a check fails, say exactly which file/line and what the fix is, then let the contributor fix it and re-run. Base to diff against: `$ARGUMENTS` (default `main` — use `develop` if that's the repo's trunk). ## Step 0 — Scope the change Determine what this PR touches. Run: - `git diff --name-status <base>...HEAD` — files added / modified / renamed / deleted. - `git diff <base>...HEAD -- CHANGELOG.md` — did the changelog move? Group the changed files by area: `skills/` (each skill's `SKILL.md` wrapper **and** its co-located `prompt.md` contract), `templates/`, `reference/`, root docs (`README.md`, `EXPLAINER.md`, `CHANGELOG.md`), `.claude-plugin/`, `scripts/`. The checks below key off which areas changed — skip a check only when nothing in its area changed, and say so. ## Step 1 — Run the automated gate (do this FIRST, don't eyeball it) The deterministic checks are **scripts**, not prose you re-perform by hand. Run them and **paste their real output** into your report; a non-zero exit is a **blocker**, full stop. - `node scripts/check-version.mjs` — version stamps agree across `plugin.json`, the README badge, and the top released `CHANGELOG.md` header. Tagging is not checked (see below); confirm...