Release Notes From Git Log Skill for Users and Developers (SKILL.md)
A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.
341 prompts · last added
119 results for “merge-decision” · page 5 of 5
A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.
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.
Converts your pasted Cursor .mdc rules into a single AGENTS.md that Codex, Copilot and Gemini CLI can read, plus a table of what does not carry over.
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.
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.
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.
Builds a tailored discovery call agenda, question bank, and qualification scorecard so a rep can decide whether to advance, nurture, or disqualify an opportunity after the call.
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.
Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.
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.
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
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.
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.
Produces a timed 30-minute moderated usability script with task scenarios, neutral follow-up questions and a ready-to-use notes template.
Compare the avalanche and snowball methods on months to debt-free and total interest using your own debts and extra payment, as education only.
Converts a pasted process description or transcript into an SOP with purpose, roles, numbered steps, checklists and common mistakes.
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.
Rewrites a long email to roughly half its length, keeps every fact and ask, puts the request up front, and shows what was cut.
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.
Organizes rough symptom notes into a dated timeline and a prioritized question list for your appointment, without any diagnosis.
Designs a four-agent pipeline for your report type with each agent's prompt, inputs, outputs and handoff format.
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.