WordPress Security Hardening and Plugin Exposure Review
Review WordPress security posture, plugin exposure, outdated components, admin access, backups, file permissions, hosting controls, and remediation priorities.
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
Review WordPress security posture, plugin exposure, outdated components, admin access, backups, file permissions, hosting controls, and remediation priorities.
Investigate WordPress plugin conflicts, theme issues, PHP errors, admin breakage, frontend failures, cache risks, and safe rollback steps.
Audit codebase documentation gaps, setup instructions, architecture notes, deployment steps, ownership, risk areas, and maintainer handoff needs.
Investigate failed GitHub Actions workflows, identify root causes, plan safe fixes, review secrets and permissions, and define verification steps.
Use Codex to trace a slow Laravel execution path, diagnose Eloquent and database performance risks, compare safe remedies, and define evidence-backed regression verification.
Audit Laravel authorization coverage across policies, gates, middleware, route protection, roles, ownership rules, denial paths, and regression tests.
Investigate Laravel queue job failures, retries, timeouts, idempotency, logs, dependencies, side effects, and safe recovery steps with Codex.
Use Codex to inspect supplied Laravel payment code and produce an evidence-linked plan for safely testing checkout, signed webhooks, idempotency, retries, refunds, entitlements, subscriptions, and manual review without implying that tests were run or changes were made.
Plan a safe migration from duplicated Laravel Blade markup to reusable components while preserving visuals, forms, data bindings, accessibility, and behavior.
Review Laravel third-party API integrations for timeouts, retries, rate limits, auth failures, idempotency, logging, fallbacks, and regression tests.
Use Codex to inspect supplied Laravel evidence and produce an evidence-linked audit-trail design and implementation plan for sensitive admin actions, covering actor attribution, authorization, transaction timing, retries, redaction, retention, integrity, access controls, and regression verification.
Audit Laravel form request validation coverage, authorization behavior, edge cases, error formats, input normalization, and regression tests before changing request rules.