Software Engineering AI prompts

Audit a pull request for production risk, missing tests, observability gaps, and a rollback plan instead of style-only review comments.

Map timeouts, retries, queues, and partial failure across a service graph so retry storms and poison messages are visible before they page you.

Design a test strategy for a risky change with the cases that would have caught the last incident, not a generic unit-test shopping list.

Review SLIs, SLOs, and alerts for a service so pages map to user pain, error budgets are usable, and dashboards answer the first on-call questions.

Plan a library or runtime upgrade with changelog risk, lockfile strategy, CI gates, and a rollback that does not leave half the fleet on a broken version.

Threat-model a service for authz gaps, tenancy leaks, injection, and abuse paths, then rank mitigations that engineering can ship before launch.

Investigate a latency or throughput regression with profiles, deploys, and query plans, then recommend a safe fix instead of a speculative rewrite.

Draft an architecture decision record with real options, consequences, and reversal cost so the team can commit without burying disagreement in chat.