Open a file, see 400 lines, close it again. Three prompts for the boring-but-important cleanup. The Claude one’s my favorite — refactor plan as a table, no rewritten code dump. Pick whichever matches your mess.
[Claude]
Given the file at [path], list every function over 40 lines, name the single responsibility each one violates, and propose a split into smaller functions with exact signatures. Output as a markdown table: function, current lines, violation, proposed split, estimated complexity saved. Do not rewrite the code, only the plan.
[ChatGPT]
Given this stack trace and the 200 lines of code that produced it, identify the root cause, then write a minimal failing test that reproduces the bug, and the one-line fix. Output as three sections: Root Cause, Failing Test (pytest), Fix. Keep the fix under 10 lines and explain why it works in one sentence.
[Cursor]
In this repo, find all TODO and FIXME comments, group them by module, and generate a prioritized backlog as a markdown table: module, comment, severity (critical/major/minor), estimated effort, suggested owner. Then create a file BACKLOG.md at the repo root with the table and a one-line next-action for the top item.
Full archive lives at aitoolalliance.com/tag/prompt-pack.