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
Use Codex to inspect a pull request, trace affected behavior, identify evidence-backed defects and regressions, assess security and operational risks, and produce a testable merge recommendation without overstating what was executed or verified.
Create an evidence-grounded plan for complex repository changes, with architecture inspection, phased implementation, migration and release controls, verification gates, rollback paths, and optional authorized execution.
Generate a repository-specific AGENTS.md for Codex with scoped editing permissions, evidence-based commands, approval gates, security controls, verification requirements, and honest completion reporting.
Use Codex to scope, design, implement, and verify the smallest useful version of an app while preserving repository conventions, controlling consequential actions, and separating proposed work from evidence-backed results.
Use Codex to conduct a read-only, evidence-grounded review of a Laravel pull request across application behavior, authorization, data migrations, queues, caches, compatibility, deployment safety, and test coverage. Findings are tied to code locations or execution evidence, while unverified work and merge authority remain explicit.
Guide Codex through evidence-based diagnosis of Laravel checkout and webhook failures, including signature validation, idempotency, retries, event ordering, payment-state integrity, and gateway compatibility. The prompt permits only authorized workspace changes and requires explicit separation of proposed, executed, unavailable, and unverified work.
Use Codex to build an evidence-backed, risk-based verification plan covering automated tests, manual checks, CI gates, observability, rollback readiness, and release confidence.
Use Codex to refactor risky legacy code in small, reversible increments while preserving observable behavior, strengthening characterization coverage, and producing evidence-backed regression, rollback, and review records.
Turn a feature request into an evidence-backed implementation or change plan with repository impact analysis, bounded code changes, regression coverage, and release verification.
Use Codex to identify measured bottlenecks, design or implement bounded optimizations, and verify performance gains without changing required behavior.
Use Codex to inspect application code for authentication, authorization, injection, unsafe input handling, secret exposure, file-access flaws, and release-blocking security risks.
Design and review production database migrations with evidence-based rollout, data protection, rollback or recovery controls, and concrete verification gates.