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.
336 prompts · last added
32 results for “call-notes” · page 1 of 2
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 turns any meeting transcript or rough notes into a decision log, owner-and-date action items, open questions and a ready-to-send recap email.
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.
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.
Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
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.
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.
Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.
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.
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.
Splits a research question across parallel research agents, defines source discovery and evidence review steps, merges findings into a citation table, and produces a decision memo without claiming live browsing.
Designs verification checks, error handling, and a self-correction loop for an agent task before it runs, based on likely failure modes.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Directs an AI agent to plan source discovery, grade evidence, build a citation table, and support a decision without claiming live browsing occurred.
Runs a behavior-preserving refactor in Codex exec. It pins current behavior with characterization tests, refactors in small verified steps inside an allowed scope, and ends with an evidence-based handoff for the merge decision.
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.
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.
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.
Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.
Guide
Nothing that fits? Write a prompt with AI.
336 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 Midjourney (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.