Root Cause Analysis from Stack Trace and Logs
Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.
341 prompts · last added
64 results for “run-ledger” · page 3 of 3
Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.
Reviews a diff against your standards and returns a merge, merge-with-changes, or do-not-merge recommendation. Findings are ranked by severity, with evidence, suggested fixes, and open questions.
Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
Claude Code inspects your repository and writes a CLAUDE.md under 200 lines with verified commands first, checkable conventions, anti-patterns and the reasons behind key decisions.
Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
Has Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
Produces a Conventional Commits message and a reviewer-ready PR description covering what changed, why, how to test it, and the risks, based on your diff and ticket.
A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.
A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.
Has Cursor lock in current behavior with characterization tests before restructuring a legacy module in small steps, so you can decide whether the refactor preserved behavior and is safe to merge.
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.
Turns a raw feature or bug request into a paste-ready Codex task with a goal, constraints, files in scope, definition of done and exact verification commands.
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
A SKILL.md that has your agent profile a messy CSV or spreadsheet, fix it in a copy with a script, and report every change so the cleaned data can be trusted.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.