Topic
Writing a good prompt for a coding assistant takes more than "fix my code." This collection gives developers ready-to-use prompts for the tasks that come up every day: finding bugs and explaining their root cause, writing unit tests that cover edge cases, reviewing a diff for readability and performance, and breaking down unfamiliar code line by line. Every prompt is free, works with any language or framework, and uses {{variable}} placeholders so you can drop in your own code and get a useful answer immediately — no prompt engineering required. Whether you're debugging a production issue, prepping a pull request, or just want a second pair of eyes on a function, start here.
53 prompts · page 5 of 6
Reviews a pasted PR or diff in two passes instead of one: the first pass lists every potential issue it can find, and the second pass critiques those findings and throws out anything weak or unsupported. The final output separates confirmed issues from possible risks and lists discarded findings with the reason they didn't hold up, which cuts down on the false alarms a single-pass review tends to produce.
Generates unit tests for a single pasted function in whatever test framework you name, without needing a full diff or surrounding file for context. Covers three buckets specifically: normal expected inputs, edge cases, and invalid inputs, written in your framework's syntax so the output can be dropped straight into a test file. A good default when you just have one function and need a quick, focused test pass.
Paste a draft agent skill or reusable prompt along with your project context, the target task, available tools, and known risks, and get back a structured audit covering purpose, required inputs, output format, safety boundaries, and failure modes. The review also flags missing checks and repeatability gaps, then returns an improved version ready to test — useful before wiring a skill into an autonomous coding agent or handing it to a team.
Submit a proposal along with your project context, stack, constraints, and team's skill level to get a skeptical second opinion before committing engineering weeks to it. The review separates what's genuinely strong from what's over-engineered, surfaces hidden coupling that will resurface later as maintenance cost, and ends with a clear verdict plus a minimal implementation path instead of just a list of concerns.
Paste a diff along with your public API surface, schema context, and configuration context to get a structured audit of breaking changes before you ship a release. It checks renamed methods, changed signatures, request or response field changes, unmigrated schema changes, environment variable renames, and altered defaults, then returns a severity-ranked table with affected users, migration paths, and a deprecation strategy where one is needed.
Feed in a stack trace, expected versus actual behavior, the relevant code, environment, recent changes, and what you've already tried when you can't tell which layer is actually failing. Returns ranked hypotheses weighed with evidence for and against each one, a step-by-step debugging plan, and both a quick fix and a proper fix so you can unblock now while scheduling the real solution.
Paste code along with its purpose, stack, module, and constraints to get a full-spectrum review covering correctness, security, performance, maintainability, error handling, accessibility, and test coverage in one pass. Returns a severity-ranked issues table, the top 3 priorities, positive observations, and specific tests to add — built to run right before merging a PR or handing code to a peer reviewer.
Give it a raw feature idea along with product context, target users, technical stack, and constraints, and get back more than a task list. It clarifies the problem statement, surfaces assumptions and open research questions, scopes an MVP with explicit out-of-scope items, then works through user stories, technical design, data model needs, implementation phases, and risks before ending with a validation plan.
Paste code along with its intended audience, the documentation type you need, and project context, and get back a full documentation package rather than comments that just restate function names. Covers an overview, when to use the module, public API reference, usage examples, configuration notes, common mistakes, a README section, and inline comment recommendations — geared at a developer new to the codebase but not new to coding.