Browse Problems
Discover prompting challenges and the community's best solutions.
Convert bug reproduction steps into automated regression tests
Bug report: '1. Login as admin, 2. Go to Reports, 3. Click Export, 4. Error appears'. Need to turn this into an automated test that prevents regression.
Bug Steps to Regression Test
Example output
Generate API endpoint names that follow REST conventions
You want to add 'get user's active subscriptions'. Need endpoint name that follows REST: GET /users/:id/subscriptions?status=active. Not: GET /getUserActiveSubscriptions.
REST Endpoint Name Generator
Example output
Detect code smells in PRs before they become technical debt
PR adds 300-line function, hardcodes API keys, uses nested loops. Need automated review that flags: 'Function too long', 'Hardcoded secret', 'O(n²) complexity'. Catch issues before merge.
Code Smell Detector
Example output
Generate database migration rollback plans before deploying
You're adding a column. Migration fails in production. Need rollback plan: (1) what to run, (2) what data to backup first, (3) what to verify after. Don't figure this out during an outage.
Migration Rollback Plan Generator
Example output
Write commit messages that explain WHY, not just WHAT
Bad commit: 'Update user model'. Good commit: 'Add email verification to user model to prevent fake signups'. Need prompts that generate commits explaining the motivation, not just the change.
Meaningful Commit Message Generator
Example output
Generate test cases from bug reports automatically
Bug report: 'Export fails when date range spans multiple years'. Need test cases: (1) single year, (2) span 2 years, (3) span 3+ years, (4) leap year boundary, (5) timezone edge cases.
Bug Report to Test Cases
Example output
Generate PR descriptions from Git diffs that reviewers can actually understand
Git diff shows 500 lines changed. Reviewer needs: 'What changed?', 'Why?', 'What to test?'. Need prompts that analyze diffs and generate: summary, motivation, testing steps, breaking changes.
Git Diff to PR Description
Example output
Parse and validate complex JSON schemas with helpful error messages
API expects nested JSON with 20 fields. User sends invalid data. Need validation that says: 'Field "items[2].price" must be number, got string "free"' - not just 'Invalid JSON'.
JSON Schema Validator with Path-Specific Errors
Example output