GitHub Copilot Pull Request Description Written From the Diff
Turns the changes in a branch into a clear pull request description: what changed and why, how to test it, risks and screenshots to add, in your repo's template if it has one.
341 prompts · last added
287 results for “Macro close-up” · page 6 of 12
Turns the changes in a branch into a clear pull request description: what changed and why, how to test it, risks and screenshots to add, in your repo's template if it has one.
Builds a day-by-day revision timetable counted back from your exam date, with practice tests, review days and buffer days sized to the hours you really have.
Has Claude Code review a branch diff like a skeptical maintainer, producing severity-ranked findings with evidence and a clear merge, fix, or block recommendation. Use it before opening or approving a pull request.
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.
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
Turns your source material into a diagnostic quiz with an answer key, a misconception map, and a reteach plan. It helps you decide who needs review and what to reteach.
Makes you into a boxed action figure with accessories in a clear blister pack, the toy-packaging trend shared across Instagram, TikTok and LinkedIn.
Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.
Tests a specific claim or statistic against primary and peer-reviewed sources. Produces an evidence grid, a contradiction log, and a calibrated confidence rating with explicit unknowns.
Audits a user flow from screenshots or descriptions and returns an evidence-labeled issue table plus a fix-now, next, defer plan for a sprint decision.
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.
Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.
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.
Turn raw interview notes or transcripts into evidence-backed themes, a quote bank, and a prioritized decision list. It keeps what customers said separate from what you infer.
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.
Combines your Docs, Sheets, meeting notes, and outside sources into one decision memo. Separates internal evidence from external research and logs conflicts, gaps, and next actions.
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.
Compares products you are choosing between using current reviews and spec sheets, with cited sources, real-world complaints and a recommendation based on how you will use it.
Finds the most likely cause of an error from the message and the relevant code, ranks other possible causes, and gives the smallest fix plus a way to prove it worked.
Turns a set of abstracts into a comparison matrix of methods, samples, findings and limits, then maps where studies agree, conflict and leave gaps for your review.
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 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 a messy list of what you did this year into a self-assessment organised by your company's review criteria, with impact stated plainly and one honest growth area.
Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.
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.