Explore Prompts

Design automated rollback tests that verify deployments can be reverted cleanly. Include data migration constraints and safe fallback paths.

Build a semantic diff summarizer: describe functional change, impacted modules, migration needs, and risks. Require it to cite tests/benchmarks that support claims.

Design UI improvements for reviewing AI-made diffs: risk highlighting, test evidence, and “what changed semantically.” Include A/B testing plan for reviewer speed/accuracy.

Create a schedule for the research agent to pull release notes, CVEs, and docs updates, summarize changes, and propose actionable backlog items with citations.

Design a doc crawler + citation store so the agent can quote authoritative sources for API usage and edge cases. Include freshness checks and version pinning.

Create a security patching playbook: small diffs, added tests, immediate canary, and post-deploy monitoring. Include coordination with human security reviewers.

Design an accessibility agent that runs audits (linting, contrast checks where applicable), proposes fixes, and validates with automated tests. Require human review for UX changes.

Create a blueprint for updating localization strings: ensure placeholders match, run i18n checks, and verify no abusive/unsafe text. Include review steps.

Design a comment improvement agent that updates misleading comments but requires linking to code references and tests to avoid stale documentation.

Create a policy for change budgets: cap number/size of automated PRs per day, prioritize highest impact, and avoid overwhelming reviewers.

Design a global kill switch that halts all automated edits/deploys across environments. Include manual override process and audit logging.

Design an agent that updates runbooks based on incidents and recurring questions. Include change review, versioning, and a “proof of usefulness” metric.