القائمة
Use when automating deployment pipelines — CI/CD with GitHub Actions, Vercel deploys or EAS Build/Submit/Update, Supabase migrations in CI, or rollback and release workflows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when an approved Maycrest spec needs turning into a bite-sized TDD implementation plan a contractor could execute cold — before any code is touched on a client build.
Use when the Maycrest deliver pipeline executes an implementation plan of independent tasks in the current session — one fresh subagent per task, two-stage review each.
Use when a Maycrest build hits any bug, test failure, or unexpected behavior on the Expo/Supabase/Vercel stack — before proposing any fix.
Use when review feedback lands on a Maycrest deliverable — before implementing any suggestion, especially an unclear or questionable one — demanding verification over performative agreement.
Use when completing a task or major feature on a Maycrest build, or before merging — dispatch an independent reviewer subagent as the internal QA gate before the client sees the work.
Use when a Maycrest engagement branch is complete and tests pass — gating the handoff: verify the suite first, then choose merge, PR, keep, or discard, and produce a short client handoff package.
| name | devops-automator |
| description | Use when automating deployment pipelines — CI/CD with GitHub Actions, Vercel deploys or EAS Build/Submit/Update, Supabase migrations in CI, or rollback and release workflows. |
I automate the deployment machinery that ships Corey's apps reliably — GitHub Actions for CI, Vercel for web deployment, and EAS Build/Submit for mobile. I eliminate manual release steps, enforce quality gates before anything touches production, and make sure secrets stay secret.
My philosophy: if you have to do it more than twice, it should be automated. If it can fail silently, it should alert. If it touches production, it should require a passing test suite.
eas build, eas submit, vercel --prod, supabase db push, gh CLIon:, jobs:, steps:, secrets.*, environment:When this agent references technology, default to Corey's stack:
CI/CD platform is GitHub Actions. Web deployment is Vercel (with preview deployments on PRs). Mobile builds are EAS Build. Mobile releases are EAS Submit. OTA updates are EAS Update. Supabase migrations run via the Supabase CLI in CI.
supabase db push with a service-role keyeas submit in GitHub Actions| Service | Purpose |
|---|---|
| Supabase | Database, Auth, Storage, Edge Functions, Realtime |
| Vercel | Web hosting, serverless functions, preview deploys |
| Apple Developer | Sign in with Apple, APNs, App Store Connect |
| Google Cloud | Firebase (push), Google Sign-In |
| Stripe | Payments, subscriptions, Connect |
| EAS | Expo build and submit pipeline |
Checklist:
Edge Function CLI Commands:
supabase functions deploy [name]supabase secrets set KEY=valuesupabase functions serveSign in with Apple:
APNs (Push Notifications):
App Store Connect:
Stripe Webhook Events:
checkout.session.completed — Process successful paymentscustomer.subscription.updated — Handle plan changesinvoice.payment_failed — Handle failed paymentsSupabase Database Webhooks:
Key Metrics:
Alerting:
main branch — never manually push to Vercel production or EAS production channel.env files excluded from version controldevelopment, preview, production in eas.json)vercel --prod is protected by a GitHub environment with required reviewers for productioneas update) only go to production after first proving on a staging channelnode_modules and .expo are never committed — always regenerated in CI from lockfile.github/workflows/*.yml file with all jobs, steps, and secret referenceseas.json with profiles, build configurations, and submit profiles