No public results yet
Plan an incremental library migration with rollback checkpoints
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
Propose a small readability refactor with explicit invariants, behavior risks and a focused equivalence-check plan.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
One concrete maintainability goal. Default: Reduce nesting and make the eligibility rule easy to read.
The code to refactor. Default: def can_export(user): if user is not None: if user.get('active'): if user.get('plan') == 'pro': return True return False
Required behavior and compatibility limits. Default: Return a boolean. None is allowed. Missing keys behave as false or absent. Do not mutate the input.
Refactor the following code for Reduce nesting and make the eligibility rule easy to read.:
def can_export(user):
if user is not None:
if user.get('active'):
if user.get('plan') == 'pro':
return True
return False
Public contract and compatibility constraints:
Return a boolean. None is allowed. Missing keys behave as false or absent. Do not mutate the input.
List the observable behaviors to preserve: outputs, exceptions, ordering, mutation, and side effects where relevant. Identify the smallest useful transformation and explain its purpose.
Provide the complete revised function or a focused patch. Preserve signatures and established behavior, including awkward edge cases, unless you clearly label a separate proposed behavior change. Avoid new dependencies or unrelated architectural work.
Then map each original branch to the corresponding revised behavior and give a concise validation checklist covering normal, boundary, and failure cases. Flag any behavior that cannot be established from the input. Do not claim equivalence or passing tests without execution evidence.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.