raycast-extensions

Derive what changed between two published versions of @raycast/api, which Raycast ships with no release notes. Fires on "what's new in @raycast/api X", "is it safe to upgrade", "derive a changelog", "they don't publish a changelog", or a pasted npmjs.com/package/@raycast/api URL. Produces a verified entry in docs/reference/raycast-api-changelog.md. Does NOT change extension code (that's `develop`) and does NOT submit anything (that's `ship`).

Change the CODE of an EXISTING Raycast extension — feature work, refactors, deliberate major dependency migrations (Node bump, ESLint major, flat-config, @raycast/api breaking changes), and bringing a forked or legacy extension up to Chris's House Style (the "house-style audit fix"). Fires on "build/add/change/refactor [feature]", "migrate to ESLint 10 / Node 22 / flat config", or "bring this fork up to my house style / fix the toasts & shortcuts to match my conventions." Does NOT scaffold net-new (that's `scaffold`) and does NOT submit to the Store (that's `ship`). Absorbs the former `raycast-extension-modernizer`.

Drive a submitted Raycast Store PR's Greptile review to 5/5 — fetch each review round, triage every finding (fix the valid, answer the invalid with receipts), re-publish, and wait for the next round WITHOUT resource-hungry polling. Fires on "address the greptile feedback", "loop until 5/5", "greptile gave us N/5", or a pasted Greptile review. Runs AFTER `ship` has opened the PR; hands code changes through the same gates ship requires. Does NOT mark the PR ready for review — that is always the user's click.

Review SOMEONE ELSE'S Raycast extension pull request against raycast/extensions — resolve the contributor's fork and head branch, sparse-fetch only the touched extension into a scratch dir, run it locally in Raycast, and report findings. Fires on "review this PR", "check out this extension PR", "run this fork locally", or a pasted github.com/raycast/extensions/pull/<N> URL. Does NOT submit your own extension (that's `ship`) and does NOT change code (that's `develop`).

Ideate and scaffold a NET-NEW Raycast extension — when no extension exists yet and you need to shape the idea, pick the command type, and lay down the manifest + first command. Fires on "create / start / scaffold a new Raycast extension." Hands off to `develop` once files exist. Do NOT use to change an existing extension (that's `develop`).

Get an existing Raycast extension into raycast/extensions and clean up — runs the pre-flight (dep hygiene + house-style AUDIT + weeding), fetches Store-compliance docs, submits the PR (via `ray publish`/`npm run publish` for monorepo extensions you contribute to, or the standalone-mirror fork-sync for your own extensions), preps the PR title/body, drives the review-feedback cycle, and sweeps merged branches. Fires on "submit / publish / ship to the Store", "npm run publish", or "address review feedback (metadata/screenshots)." Does NOT change code behavior — if feedback needs code, hands BACK to `develop`.