一键导入
handover
Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | handover |
| description | Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work. |
This command generates and saves a markdown file. Always:
./handoff-summary-YYYYMMDD-HHMMSS.mdThe purpose is file creation, not just information display.
Generate comprehensive summary for AI agent handoff: $ARGUMENTS What This Command Does This command creates a detailed markdown summary of our entire conversation, structured to enable another AI agent to seamlessly continue the work. The summary includes:
Context and Background: Initial problem statement and user requirements Work Completed: Detailed list of all tasks accomplished Technical Decisions: Key architectural and implementation choices made Code Changes: Summary of files modified, created, or refactored Current State: Where the project stands now Pending Items: Any unfinished tasks or future considerations Important Notes: Critical information for continuation
Output Format The command generates a markdown file with the following structure: markdown# Project Handoff Summary Generated: [timestamp]
Brief description of the project and main objectives
...
Current state of the codebase:
...
Key code snippets demonstrating important implementations
Recommended actions for continuing the work
Any other relevant information for smooth continuation Benefits of This Summary
Continuity: New agent can pick up exactly where we left off Context Preservation: All important decisions and rationale are documented Efficiency: Reduces need to re-explain or rediscover information Clarity: Structured format makes information easy to find Completeness: Captures both technical and conversational context
Usage Examples Basic usage: Generate handoff summary for current conversation With specific focus: Generate handoff summary focusing on authentication implementation For specific date range: Generate handoff summary for work done today Key Sections Explained User Context Captures communication preferences, technical level, and any specific requirements mentioned during conversation Technical Decisions Documents why certain approaches were chosen over others, preventing future agents from undoing intentional choices Code Examples Includes actual code snippets for complex implementations, ensuring the next agent understands the implementation style Important Warnings Highlights any critical information that could cause issues if not known (e.g., "Don't modify X because it will break Y") Related Files Lists all files that were created or modified, with brief descriptions of their purpose and changes Notes for the Next Agent The summary will include:
Conversation tone and style preferences Any tools or commands created during the session User's stated preferences (e.g., no emojis, no conventional commit prefixes) Current working directory and environment setup Any external dependencies or API keys mentioned
Output Options The command will:
Generate a comprehensive markdown file Save it as handoff-summary-[timestamp].md Display the content for review Optionally include conversation transcript excerpts for critical decisions
This ensures perfect continuity when switching between AI agents or resuming work after a break.
Transform verbose natural language requests into structured bilingual documentation (Korean for review + English for AI prompts). Use when you need to clarify and structure a complex request before implementation.
Review current git changes or latest commit using code-reviewer and architect-reviewer agents. Use after completing code changes to get comprehensive quality feedback.
Review comments and suggest cleanup (identify unnecessary comments, recommend improvements). Use to aggressively clean up comment debt in code.
Generate Conventional Commits-compliant messages (feat/fix/docs/chore) in Korean and English. Use when you need to create a well-structured commit message for staged changes.
Identify and safely remove dead code, deprecated code, and unused exports from codebase. Use when you need to clean up unused or obsolete code.
Generate business rule documentation from domain knowledge and requirements. Use when documenting complex business logic.