DovesDataViewer

Set the session to work off the BETA branch. Use when the user says "work from beta" (or "work off beta", "start from beta"). Fetches everything, prunes, and starts a fresh working branch rebased on the latest origin/BETA; for the rest of the session all work is committed to that branch and PR'd into BETA when complete. A stopgap until branch selection exists on mobile so the user doesn't have to send the full setup prompt every time.

Deep, multi-agent release-gate review of a BETA → main pull request (the release PR), posted as a report comment on the PR. Use when the user asks to "review the beta to main PR", "review the release PR", "is beta ready to merge into main", "release review", or "gate the release". Reviews the PR DIFF (everything on BETA since it diverged from main), runs fixed dimensions with adversarial verification, and produces a severity-sorted report plus an explicit GO / GO-WITH-FIXES / NO-GO verdict — then posts it as a PR comment. For a whole-codebase audit use `codebase-review`; for an arbitrary working diff use the built-in `code-review`.

Prepare the BETA branch for release into main. Use when the user wants to "prep beta", "cut a release", "get beta ready for main", or "do release prep". Researches every commit between the last release tag and BETA to verify the CHANGELOG is complete and to build release notes, creates a release branch off BETA, flips the eye-in-the-sky coach plugin from the BETA git dependency to the published production npm package, sets the version in package.json to match the topmost unreleased CHANGELOG heading, dates that heading to today, runs the green-before-merge checks, opens a PR into BETA, ensures a BETA→main PR exists whose body is copy-paste-ready release notes, and opens a follow-up "flip coach back to BETA" PR to merge after release. Documents the manual post-release tag + back-merge of main into BETA. Never creates tags.

Deep, multi-agent professional code-review audit of the WHOLE codebase (not the working diff). Use when the user asks for a "deep dive", "harsh review", "audit", "professional review", "find all the issues", or otherwise wants a prioritized backlog of everything wrong with the project — architecture/modularity, coupling, god files, security, performance, testing/regression coverage, and CI. Produces a single severity-sorted Markdown report. For reviewing the current diff/PR instead, use the built-in `code-review` skill.