Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.
341 prompts · last added
79 results for “the box art style” · page 2 of 4
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.
Has Codex review a pull request and return comments sorted into blocking, should-fix and nit, each with the file and line, the risk, and a suggested change.
Directs Claude Code to reproduce a reported bug with a failing test, apply the smallest fix, and prove the fix with command output. Use it to decide whether a bug is fixed and safe to merge.
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
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.
Has GitHub Copilot review your branch diff against the base branch, flag defects and missing tests, and draft a PR description with evidence. Use it to decide whether to open the PR or fix issues first.
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.
Designs the handoff contracts, stop conditions, and review gates for a sequential chain such as researcher, writer, editor, and fact-checker. Helps you decide whether the chain is ready to run.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Designs a three-agent content pipeline where a researcher, writer and editor pass structured handoffs, with the exact fields each agent receives and returns and checks between stages.
Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
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.
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.
Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.
Builds a regular expression from a plain-English description and example strings, explains each part, and proves it against strings that should and should not match.
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.
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.
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.
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.
Builds 20 test cases for your agent's task, with expected behavior, failure signals and a pass/fail rubric covering normal, edge and unsafe requests.
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
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.