ai-review-integrationDesign, implement or assess an automated AI reviewer integrated with GitLab merge requests: isolate a trusted controller from contributor-controlled code and model output, pin analysis to one immutable MR version, account for every changed file despite API limits, validate structured findings, and p
ci-pipeline-designDesign a CI/CD pipeline, or restructure one that grew badly: decide which checks may block a merge before drawing any stage, lay the stages out as a dependency graph so nothing waits on unused output, key caches on what actually invalidates them, choose a matrix or separate jobs, build the artefact
cutoverPlan and run a high-stakes, hard-to-reverse switchover to completion — a DNS or traffic switch to a new system, a datacentre or region move, a hosting or vendor swap, a monolith-to-service carve-out with a big-bang or gradual shift, a database failover or promotion. Produces the numbered runbook wit
db-migrationShip a schema change to a live relational database without downtime, a stuck lock, or a deploy that cannot be reverted: expand, backfill in bounded batches, migrate reads, migrate writes, contract — each phase its own independently revertible deploy, every migration session carrying an explicit lock
feature-flag-lifecycleImplement and retire a feature flag safely after the rollout mechanism has been chosen. Use when wiring a flag into request, client or worker code, making subject assignment sticky, choosing safe behaviour when configuration is unavailable or stale, exercising a kill switch, proving the off path, or
gitops-operationsOperate Argo CD without fighting the controller: establish which repository and generator own desired state, explain OutOfSync and drift, review rendered changes before sync, order dependencies, choose prune and self-heal policy, recover by changing Git, and verify convergence from commit to workloa
mobile-releaseShip a native iOS or Android build through the app store's own phased or staged rollout, where the binary itself cannot be recalled once installed. Gate every stage on an agreed crash-free-rate comparison between the new version and the previous one at the same install age, set the halt threshold be
pipeline-hardeningHarden or audit a CI workflow, GitHub Actions first, GitLab CI too: untrusted PR title, branch, comment or fork code reaching a run: step; pull_request_target, workflow_run or issue_comment plus checkout of untrusted code; token/secret reach per job; actions/tools pinned to a SHA, tag recorded; long
plan-platform-migrationPlan and review migrations of production platforms, services, data, infrastructure, CI systems, observability stacks, identity systems, or developer tooling from one operating state to another. Produces a phased plan with explicit invariants, dependency and state inventories, compatibility strategy,
release-notesTurn a range of merged changes into release notes the affected reader can act on, and run the release gates: derive the range from the last shipped tag, not a date, sort entries by who is affected instead of by component, write each breaking change with its migration, cut the noise, resolve the ambi
release-strategyGet a change into production gradually, so that being wrong costs a fraction of users rather than all of them — separate deploy from release, choose the mechanism (feature flag, percentage or ring rollout, blue/green, shadow traffic) from how the change fails, design rings and bake times that cross
safe-backfillRun a standalone production data repair or reprocessing pass without losing progress or overwriting newer writes. Use when asked to fix existing records at scale, replay a bounded set of records, resume a halted repair, design a checkpointed data job, or prove that a repair actually converged. Freez