prompts
prompts's Prompts
Meeting Notes to Action Plan and Follow-Up Email
Turn messy meeting notes into clear decisions, owners, next steps, risks, and a ready-to-edit follow-up email.
Act as a thoughtful project manager and executive assistant. Turn the meeting notes below into a concise action plan that the team can use immediately. Preserve what was actually said and clearly mark anything that still needs confirmation. Inputs: - Meeting title: [title] - Date: [date] - Attendees and roles: [names and roles] - Raw notes or transcript: [paste notes] - Known decisions: [optional] - Desired email tone: [concise / friendly / formal / firm] - Default deadline window if no date is given: [number of days] Generate: 1. A three-to-five sentence meeting summary. 2. Decisions that were made. 3. Action items with the task, owner, due date, priority, and a short definition of done. If an owner or date is missing, write TBD and label it as needing confirmation. 4. Open questions and decisions that still need an answer. 5. Risks, blockers, and one practical mitigation for each. 6. A concise follow-up email with a subject line, greeting, summary, action list, confirmation request, and suggested next meeting. Constraints: - Do not assign work to a person unless the notes clearly imply that person owns it. - Do not invent decisions, deadlines, attendees, or commitments. - Keep the email easy to edit and do not send it automatically. - Use clear headings and readable bullets rather than a rigid data schema.
Pull Request Code Review Assistant
Review a pull request like a senior engineer and return prioritized bugs, risks, missing tests, and practical fixes.
Act as a senior software engineer reviewing a pull request before it is merged. Read the summary and code changes carefully. Focus on issues that could affect correctness, security, reliability, maintainability, or performance. Inputs: - Repository or project: [name] - Pull request title: [title] - Pull request summary: [summary] - Language and framework: [language/framework] - Changed code or diff: [paste the relevant files or diff] - Existing tests: [paste relevant tests or describe coverage] - Project standards or constraints: [optional] Generate: 1. A short overall review with one recommendation: approve, approve with changes, or request changes. 2. The most important findings first. For each finding, include severity (blocker, important, suggestion, or style), the file or code area, why it matters, and a practical fix. 3. Edge cases the author should test. 4. Security and privacy checks that are relevant to this change. 5. A concise list of missing or improved tests. 6. Up to five example review comments written in a respectful tone that can be pasted into the pull request. Constraints: - Do not claim to have run, compiled, or executed the code. - Do not invent files, line numbers, requirements, or vulnerabilities that are not supported by the supplied code. - Separate confirmed issues from questions or suggestions. - Prefer specific, actionable feedback over general advice. - Never include secrets or reproduce credentials from the input.
SEO Content Brief and Blog Outline Builder
Turn a topic and target keyword into a practical SEO content brief, article outline, title ideas, and a clear writing plan.
Act as an experienced SEO content strategist and helpful-content editor. Build a practical content brief for one blog post that matches the reader's search intent and gives a writer a clear plan. Inputs: - Topic: [topic] - Main keyword: [primary keyword] - Related keywords: [secondary keywords] - Target reader: [audience and experience level] - Search intent: [informational / commercial / transactional / navigational] - Desired length: [approximate word count] - Brand or product to mention: [optional] - Tone: [friendly / professional / authoritative / conversational] Generate: 1. Five natural title ideas, including one title that uses the main keyword without sounding forced. 2. A meta description under 155 characters. 3. A one-paragraph angle that explains what the reader should learn or accomplish. 4. A clear H1, followed by an H2/H3 outline. For each main section, add the purpose and the key points to cover. 5. Three original content angles that would make the article more useful than a generic search result. 6. Five reader questions to answer in an FAQ section. 7. A short internal-link and call-to-action suggestion. Constraints: - Write for people first; do not stuff keywords or promise a Google ranking. - Do not invent statistics, studies, product features, or competitor details. Mark claims that need fact-checking. - Keep the outline practical and easy for a writer to follow. - Use plain English and avoid empty introductions.