Pr review pipeline
Reviews a pull request in layers: understand, correctness, security, tests, style, then a verdict.
Reviews a pull request in layers: understand, correctness, security, tests, style, then a verdict.
Migrates code between frameworks or versions in small steps that each keep tests green.
Walks a release from freeze to post-release check: changes, tests, notes, deploy, monitor and rollback plan.
Generates a useful test suite for a module: behaviours, edge cases, tests and a mutation check.
Turns a pile of feedback into themes, counts, quotes and recommended actions for the product team.
A layered security review of a feature: map, threats, code checks, dependencies and fixes.
A monthly routine to check competitors' pages, pricing and announcements and summarise what changed.
Weekly newsletter production: pick stories, write sections, subject lines, proof and schedule.
Turns one long piece into posts, an email, a short script and quotes for different channels.
Turns a long video script or transcript into several short clips with hooks and captions.
Researches a prospect from public sources and drafts a short, specific outreach email for your review.
Refreshes an old page for search: check intent, find gaps, update content, titles and links.
Turns a meeting transcript into decisions, tasks with owners and a follow-up email.
A safe routine to profile, clean and validate a dataset, with a log of every change.
Builds a sourced research report: question, sources, notes, synthesis, draft and fact-check.
Builds an onboarding pack for a new team member: setup guide, first-week plan and glossary.
Takes an incident from raw facts to a blameless review with actions and owners.
Prepares a job application: analyse the role, tailor the resume and cover letter, prepare for interviews.
From topic to published-ready blog post: research, outline, draft, edit and meta tags in five checked steps.
Designs a short course: audience, outcomes, modules, lessons, exercises and assessment.
Turns a week of scattered notes into a clear status report for your manager or team.
Plans a launch: goals, audience, message, channels, timeline, owners and success measures.
A bug-fixing flow: reproduce, find the cause, write a failing test, fix, verify and summarise.
Turns solved support tickets into help centre articles and updates the macros.
Kept in this browser only. Clearing site data will remove them.
Free account needed to copy more
Create a free account to save prompts on every device, download whole guides as files, and get the best new prompts each week.
Already a member? Sign in