Plan a reversible package uninstall
Checks which files and settings are truly owned.
[INSTALL MANIFEST][CURRENT FILE LIST][USER DATA RULES]
Topic · 32 prompts
Coding & development
Explore coding & development prompts with clear inputs, complete instructions and ways to adapt the result. Explore “Plan a reversible package uninstall” and “Find hidden coupling among tests”.
Find hidden coupling among tests
Prevents order-dependent false confidence.
[TEST SUITE][SHARED FIXTURES][FAILURE PATTERN]
Trace character corruption through a pipeline
Finds where text changes encoding.
[INPUT SAMPLE][PIPELINE STEPS][EXPECTED OUTPUT]
Check that dry-run matches real planned actions
Ensures preview cannot hide dangerous differences.
[CLI CODE][ACTION TYPES][TEST FIXTURES]
Define cache invalidation from user-visible examples
Maps mutations to exact stale views.
[CACHE KEYS][MUTATIONS][READ PATHS]
Prevent spreadsheet formula execution in exports
Treats cell text as untrusted data.
[EXPORT CODE][FIELD LIST][TARGET SPREADSHEET]
Test pagination at its boundaries
Protects clients from skipped or repeated records.
[PAGINATION CONTRACT][SAMPLE RESPONSES][SORT KEY]
Explain why two builds differ
Inspects inputs before blaming the compiler.
[BUILD COMMANDS][MANIFESTS][ARTIFACT HASHES]
Keep secrets out of application logs
Tests specific error paths for sensitive output.
[LOGGING CODE][SENSITIVE FIELDS][SAMPLE EVENTS]
Review permission checks in an endpoint
Finds paths that reach data before authorisation.
[ENDPOINT CODE][ROLE RULES][REQUEST EXAMPLES]
Prove a serializer can round-trip values
Protects meaning across encoding boundaries.
[DATA SCHEMA][SERIALIZER CODE][EDGE VALUES]
Test a parser against malformed inputs
Makes failure behaviour explicit before implementation.
[PARSER CONTRACT][INPUT EXAMPLES][LANGUAGE]
Prove a backup can restore into a safe test environment
Defines a non-production restore rehearsal with integrity checks.
[BACKUP FORMAT][TEST ENVIRONMENT][RECOVERY OBJECTIVE]
Remove a stale feature flag without changing behaviour
Traces call sites, data variants and rollout assumptions first.
[FEATURE FLAG][REPOSITORY]
Make command-line errors actionable and stable
Designs exit codes and messages for predictable failure handling.
[CLI COMMANDS][FAILURE CASES][AUTOMATION USERS]
Prepare evidence before upgrading a dependency
Maps API changes, lockfile effects and rollback for a package update.
[DEPENDENCY][CURRENT VERSION][TARGET VERSION]
Design an offline action queue with visible conflicts
Defines replay order, idempotency and user-facing conflict states.
[USER ACTIONS][SYNC API][CONFLICT RULES]
Test date logic at the boundaries that break it
Generates cases for timezone, daylight and period-edge behaviour.
[DATE FUNCTION][BUSINESS TIMEZONE][EXPECTED RULE][LANGUAGE]
Make a file importer safe to rerun
Specifies identity keys, partial-failure behaviour and tests.
[INPUT FORMAT][TARGET SCHEMA][IMPORT RULES]
Review a configuration change for unintended effects
Maps a proposed config diff to environments, defaults and rollback.
[CONFIG DIFF][ENVIRONMENTS][SERVICE CONTRACT]
Protect a legacy function before refactoring
Builds tests around observed behaviour, including awkward quirks.
[FUNCTION CODE][LANGUAGE OR FRAMEWORK]
Generate concurrency tests from a workflow
Exposes double-submit and race problems.
[WORKFLOW DESCRIPTION][STATE TRANSITIONS]
Find the forgotten UI states
Reviews a component beyond the happy path.
[COMPONENT SOURCE][USER JOURNEY]
Storyboard failures before implementing an API
Makes retry, timeout and partial success behaviour concrete.
[API WORKFLOW][KNOWN CONTRACT]