APromptAura

#refactoring

Top prompts tagged refactoring.

0
p/codingAauraNovice4 days agohas example⁂auto-checked

Simplify deeply nested conditionals without changing behavior

Simplify the deeply nested if/else or switch logic below. Rules: 1. Preserve behavior exactly, including any subtle order-dependent checks (list any you find, so I can confirm you preserved them correctly). 2. Prefer guard clauses / early returns over nested if-else pyramids. 3. Where multiple conditions test the same variable, consider whether a lookup table, strategy map, or polymorphism would be clearer than a long conditional chain, but only propose it if it's genuinely simpler here, not as a default pattern. 4. Compute cyclomatic complexity (rough count of independent paths) before and after, so I can see the actual improvement. 5. If any branch is unreachable or looks like dead code given the earlier conditions, flag it separately, don't silently delete it, since dead-looking code is sometimes defending against a case I haven't told you about. Code: code Language: language
ClaudeGPT#refactoring#clean-code#complexity
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Convert imperative loop-heavy code to functional style without losing clarity

Rewrite this code from an imperative, loop-and-mutation style into a functional style using language's idiomatic map/filter/reduce (or equivalent) constructs. Constraints: 1. Only do this where it genuinely improves readability; if a loop is already the clearest way to express the logic (e.g. it has early exits, multiple accumulators, or complex control flow), say so and leave it as a loop rather than forcing a functional rewrite that would be harder to read. 2. Preserve exact behavior including edge cases (empty input, short-circuit behavior). 3. Avoid deeply chained one-liners that sacrifice readability for cleverness; prefer named intermediate variables over a 5-deep chain. 4. Note any performance implications (e.g. multiple passes over the array instead of one) and whether that matters given the expected data size. 5. Show before and after, and a one-line justification for each change. Code: code Expected data size / performance sensitivity: data_size_context
ClaudeGPT#refactoring#functional-programming#clean-code
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Turn a god function into composable, testable units

I have a function that has grown too large and does too many things. Refactor it into smaller, single-responsibility functions or classes, following these constraints: 1. Preserve the exact external behavior and public signature unless I say otherwise. 2. Extract pure logic (no I/O, no side effects) into its own functions first, so they can be unit tested without mocks. 3. Name each extracted piece for what it does, not how it does it. 4. Show the before/after side by side for the riskiest extracted piece, with a one-line note on why it is now safer to change. 5. List any behavior that is ambiguous in the original code (e.g. unclear error handling, implicit ordering dependencies) that I should confirm before shipping this refactor. 6. Do not introduce new dependencies or design patterns beyond what the language's standard idioms support. Language/framework: language Function to refactor: code What it's used for / calling context: context
ClaudeGPT#refactoring#clean-code#testing
0