Plan a major dependency upgrade
Prepare for a major library or framework upgrade: breaking changes, code to update and a safe rollout order.
@lazyprompt
Starter prompts curated by the LazyPrompt team.Prepare for a major library or framework upgrade: breaking changes, code to update and a safe rollout order.
Draft a design doc with goals, options, a recommendation and risks, ready for team review.
Turn feature requirements into a normalized schema with keys, constraints, indexes and the tradeoffs explained.
Find why a build or pipeline fails in CI but not locally, and get the exact change to fix it.
Port code to another language so it reads like native code, with notes on behavior differences and gotchas.
Generate a practical README for a project: what it is, quick start, usage examples and contribution notes.
Systematically narrow down why a test or bug only fails sometimes, with experiments to prove the cause.
Draft a clear, tight system prompt that tells an AI coding assistant how to work in your repository.
Paste a profile, flame graph summary or timings and get a ranked list of real bottlenecks with what to try first.
Audit code or a feature design for vulnerabilities, mapped to realistic attack scenarios and fixes.
Create a PR description that helps reviewers understand the change, how to test it and what to watch for.
Turn a diff or a rough description into a clean commit message that explains the why, not just the what.
Plan a database, framework or infrastructure migration with phases, rollback points and verification at each step.
Review an API design for consistency, evolvability, error handling and security before you ship it.
Describe what you want to match and get a commented regex with matching and non-matching test cases.
Find why a query is slow and get a faster version, index suggestions and a way to prove the improvement.
Describe the question and your tables, and get a correct, readable query with an explanation and edge cases.
Understand code you inherited: a layered explanation from the big picture down to the tricky lines.
Plan a refactor as small, reversible steps that keep tests green, instead of a risky big rewrite.
Generate a well-organized test suite covering happy paths, edge cases and failure modes for code you paste in.
Turn an error message and stack trace into ranked root-cause hypotheses, quick checks to confirm each, and a fix.
Get a prioritized code review that separates real defects from style nits, with a concrete fix for each issue.
Write a short, professional resignation letter and a handoff plan that protects your reputation and references.
Organize your evidence into a persuasive promotion document and a script for the conversation with your manager.