pr-review

This posts a REAL review to GitHub or Gitea (comments, and an approve/request-changes/comment verdict). It fetches a pull request's diff, runs the same multi-agent analysis as `review-full`, applies any project-specific review rules, then submits the review via the platform's API. For reviewing local diffs that aren't an open PR, use `review-full` or `review-diff` instead. ## Step 0: Resolve the PR and detect the platform - Determine the target PR from `$ARGUMENTS` (a number or URL). If empty, detect the PR for the current branch. - Detect the git host from `git remote get-url origin`: - `github.com` -> **GitHub**. Use the `gh` CLI (assume it is already authenticated). - Anything else (self-hosted Gitea/Forgejo/Gogs, e.g. a company git server) -> **Gitea-style REST API** via `curl`. - For Gitea, locate this project's own credentials rather than asking every time: - Check whether the project's `CLAUDE.md` `@import`s a credentials file (commonly `rules/credentials.md`; this mirrors a common per-project credentials-import convention). - If none is found, ask the user for the base URL and a `username:token`, and offer to save them into a **new, gitignored** file (e.g. `rules/credentials.md`). Never write real secrets into a tracked file, an `.example` template, or any file already committed to git. ## Step 1: Load PR context - Fetch PR metadata (title, author, base/head branch, mergeable state, description) and the unified diff: - GitHub: `gh pr view <N> --json titl...