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
276 results for “Replace the furniture” · page 6 of 12
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.
Build a topic cluster from a keyword list and existing content, then rank which cluster and pages to create first. It includes a keyword-to-page mapping table, internal link rules, and cannibalization risks.
A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.
Diagnoses where a workflow slows down using your process steps and metrics, then ranks causes and produces a 30-day improvement plan with owners, measures, and risks.
Create a ranked risk register, early warning signs, and a two-week action plan for a project. Supports the go/no-go and resourcing decision at the next checkpoint.
Convert a call transcript or notes into a concise follow-up email, structured CRM notes, and a risk check on the deal. Helps the rep decide the next step and what to say.
Upload a CSV or XLSX and get a metrics review with variance explanations, data-quality flags, and a decision list for the week. Written for ChatGPT's Advanced Data Analysis.
Plan a custom GPT before building it. Produces the instruction text, knowledge file plan, conversation starters, and a test set so you can decide whether to build, narrow, or skip it.
Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.
Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.
Analyzes weekly KPI data against targets, separates signal from noise, proposes ranked root-cause hypotheses, and produces owner-assigned actions and an escalation list for a team operating review.
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
Plans 30 days of posts that lead to one offer: content pillars, a mix of value, proof and ask posts, hooks for each day, and the platform and format to use.
Builds a customer persona from your actual reviews or survey answers: jobs, pains, words they use, objections and buying triggers, with quotes as evidence and no invented demographics.
Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.
Rewrites text that sounds machine-generated by removing the specific tells, like stock words and forced triads, while keeping every claim and the meaning.
Turns raw meeting notes or a transcript into decisions, action items with owners and dates, open questions, and a short follow-up email you can send right after the call.
Takes one piece of news or a request and rewrites it three ways, each matched to the reader's relationship, what they care about and the right level of formality.
Turns a side-business idea into a one-page plan: customer, offer, price, channel, costs, and the cheapest 30-day test that would prove people will pay.
Turns one article into ten posts for LinkedIn, X, Instagram and email, each built on a different idea from the piece, written natively for the platform rather than as a summary.
Turns the transcript of a recorded walkthrough into a numbered SOP with prerequisites, steps, screenshots to capture, decision points, and common mistakes, ready for a team wiki.
Interviews you about a task you do over and over, then writes a complete, save-ready SKILL.md with a trigger description, steps, output format and stop conditions.
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Gives codex exec a non-interactive procedure to diagnose a failing CI output, apply a minimal fix, rerun the checks and stop after three attempts with a clear report.
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.