Laravel Feature Flag Rollout and Rollback Planner
Plan Laravel feature flag rollouts with safe defaults, rollout stages, kill-switch behavior, tests, cache/config checks, queue considerations, migration safety, and rollback verification.
Category
Prompts for debugging, refactoring, building features, reviewing security, improving performance, and guiding Codex through safe code changes.
Help keep Amo.ng free and public
Plan Laravel feature flag rollouts with safe defaults, rollout stages, kill-switch behavior, tests, cache/config checks, queue considerations, migration safety, and rollback verification.
Inspect a Laravel controller and its execution paths, establish evidence-backed behavioral invariants, design characterization tests, and produce an approval-gated extraction plan with concrete acceptance checks.
Guide Codex through evidence-based legacy module inspection, behavior mapping, regression-risk analysis, and characterization test design before a risky refactor.
Use Codex to produce an evidence-based safety review of proposed Laravel schema and data migrations, including engine-specific lock analysis, rolling-release compatibility, backfill controls, recovery planning, and measurable deployment acceptance criteria.
A Codex coding prompt for proposing and, when authorized, implementing one metadata-driven static site system that serves distinct sale, ecosystem, active-destination, and fallback pages by hostname. It includes Cloudflare Workers controls, domain-inventory reconciliation, SEO checks, active-domain safeguards, and evidence-based reporting without assuming deployment or provider access.
Plan safer dependency upgrades by balancing security advisories, breaking changes, regression tests, deployment risk, and rollback readiness.
Use Codex to connect production logs to code paths, identify root cause hypotheses, and plan the smallest safe patch with verification and rollback steps.
Guide Codex to create regression tests that protect API request, response, validation, authentication, permission, and error contracts.
Use Codex to reproduce a frontend state defect, trace its causal state transition, implement an authorized minimal patch, and produce evidence-backed regression verification.
Guide Codex to build controlled profiling experiments, rank bottleneck hypotheses, and define evidence-based optimization, verification, and rollback decisions.
Use Codex to perform an evidence-based review of supplied CI/CD workflows, deployment scripts, migration behavior, configuration controls, observability, rollback readiness, and release verification plans without implying that production actions occurred.
Use Codex to inspect available incident evidence and repository context, rank root-cause hypotheses, compare containment and recovery options, and produce authorization-aware hotfix, rollback, verification, and monitoring plans without overstating execution.