一键导入
summarize
Summarizes meeting notes, transcripts, or discussions into actionable insights and follow-up items
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Summarizes meeting notes, transcripts, or discussions into actionable insights and follow-up items
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.
Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).
Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.
Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions
| name | summarize |
| description | Summarizes meeting notes, transcripts, or discussions into actionable insights and follow-up items |
Analyze and summarize the meeting content: $ARGUMENTS
Please create a comprehensive meeting summary:
Content Analysis:
Meeting Overview:
Key Discussion Points: Organize content into clear sections:
Action Items Extraction: For each action item, identify:
Decision Log:
Follow-up Requirements:
Insights and Analysis:
Communication Plan:
Professional Formatting: Present as a clean, organized summary with:
Please provide a comprehensive meeting summary that serves as a reliable record and enables effective follow-through on all discussed items.
Example output format:
Date: July 31, 2024 Attendees: John (PM), Sarah (Dev), Mike (Design)
question tool for EVERY user interaction — never ask questions as plain text