NasserAlbusaidi

automerge

Review-gated auto-merge for Rihla PRs. Classifies a PR's diff; Gate-exempt PRs (docs, token sweeps, one-sentence diffs) get GitHub native auto-merge enabled immediately so they merge on green `readiness`. Gate-category PRs (money math / firestore.rules / Cloud Functions auth / routing / schema-field-name) get a fresh-context Opus diff review, then an independent refuter, and auto-merge is enabled ONLY if both clear. Use when asked to "auto-merge this PR", "/automerge <N>", or under /loop to sweep open PRs.

deploy-ceremony

Deploy the Rihla Firebase backend (Cloud Functions + Firestore rules + indexes) to prod and keep the deploy state honest. Shows the merged-but-undeployed delta first (pending_deploy.sh), runs the commit-bound deploy + prod-state verify, advances the `backend-deployed` source-of-truth tag, then records the deploy in docs/DEPLOY-LEDGER.md and clears stale "⚠️ NOT deployed" flags. Use when asked to "deploy the backend", "run the deploy ceremony", "ship the functions", or after merging a Functions/rules PR.

grill-my-architecture

Brutal staff-engineer review of system architecture — service/module boundaries, data ownership, communication patterns, failure modes, scaling, security trust boundaries, evolvability, cognitive load, cost. Accepts an architecture doc, a set of ADRs, a system design write-up, a diagram pack, a verbal sketch, OR the codebase itself (the skill reconstructs the de-facto architecture from the code when no doc exists). Distinct from `grill-my-code` (file/function craft), `grill-my-backend` (server-side surface within one service), `grill-my-plan` (a specific planned change before code is written), `improve-codebase-architecture` (constructive refactoring opportunities), and `plan-eng-review` / `plan-ceo-review` (constructive walkthroughs). Use when the unit of critique is the *system shape*, not a file or a feature. Triggers on "grill my architecture", "grill the system design", "grill these ADRs", "is this architecture going to survive", "tear apart this design", "review my system design brutally", "stress-test

API & Backend Listed

grill-my-backend

Brutal staff-engineer review of backend code — handlers, services, migrations, background jobs, queries, integrations. Backend-specific principle library (API contract, authn/authz/tenancy, persistence & transactions, schema migrations, jobs & messaging, caching, external integration, backend ops) layered on top of `grill-my-code`'s general craft library. Use when the surface is explicitly server-side; use `grill-my-code` when the surface is generic. If in doubt, pick this one — it strictly supersets the general library for server-side code. Distinct from `grill-me` (Socratic interview) and `grill-with-docs` (aligns plan against CONTEXT.md). Triggers on "grill my backend", "grill this endpoint", "grill this migration", "grill this query", "review my API brutally", "is this handler safe".

pr-babysitter

Owns the merge tail for Rihla PRs — the stretch between "auto-merge enabled" and "actually merged" that GitHub never finishes on its own. Each pass updates BEHIND branches (auto-merge never self-updates them), runs /automerge on open PRs that lack it, surfaces P1-commented / red-CI / conflicted PRs, checks for pending backend deploys after merges, and GCs worktrees whose PR merged. Use when asked to "babysit the PRs", "watch the merge queue", "/pr-babysitter", or under /loop to run until the board is clear.

API & Backend Listed

run-the-gate

Fresh-context spec review before implementation for Rihla money/rules/routing/schema changes. Spawns TWO parallel zero-history Opus subagents per round — a rubric reviewer (7 verification principles) and an orthogonal-axis adversary (off-map regressions, derived surfaces, l10n pairs) — applies the union of P1 findings, and re-runs until both verdicts are clean in the same round. Use before writing code that touches BalanceCalculator/MoneySerializer, firestore.rules or Cloud Functions auth, app_router.dart / deep-links / back-guards, or any field-name/schema change with both a read-path and a write-path. Use when asked to "run the Gate", "gate this spec", or "fresh-context review".