CodeRabbit PR Review Fix

Preconditions

1. Node.js 20+ (LTS; native fetch is available from 18, 20 is the floor). The fetch script has zero npm dependencies.
2. BITBUCKET_EMAIL + BITBUCKET_API_TOKEN available in the environment (Atlassian API token, NOT an app password — Atlassian deprecated those). If both are missing, the script prints setup instructions on stderr and exits 1; relay them and stop.
   • bash / zsh: export BITBUCKET_EMAIL="you@example.com" and export BITBUCKET_API_TOKEN="ATATT3xFfGF0..."
   • PowerShell: $env:BITBUCKET_EMAIL = "you@example.com" and $env:BITBUCKET_API_TOKEN = "ATATT3xFfGF0..."
   • Generate a token at https://id.atlassian.com/manage-profile/security/api-tokens → "Create API token with scopes" → app = Bitbucket → scopes: read:pullrequest, write:pullrequest, read:repository.
   • Fallback (any agent): put BITBUCKET_EMAIL / BITBUCKET_API_TOKEN in a .env file at the repo root — the script reads it when env vars are absent.
3. Bitbucket target (workspace + repo). The script resolves it in this order: --workspace/--repo flags → BITBUCKET_WORKSPACE/BITBUCKET_REPO env → parsed from the origin git remote when it points at bitbucket.org/<ws>/<repo>. There is no hardcoded default (this skill is shared across teams). If none resolve, the script errors with these options — relay them. When the working repo's origin is its Bitbucket clone, no config is needed.
4. Working directory is the repo root with clean-ish git state. If uncommitted changes exist on tracked files, warn the user before applying fixes.
5. Current git branch maps to an open PR. If not, ask the user for the PR number.

Codex setup

Codex runs scripts in a sandbox that by default (a) blocks network and (b) strips *TOKEN* env vars. Before first use under Codex, add to ~/.codex/config.toml: