메뉴
Compact the current conversation into a handoff document for another agent to pick up.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Git worktree management best practices for git worktree, bare repo layouts, parallel branches, stale base sync, branch cleanup, wrong-path recovery, fork remotes, and PR review worktrees. Use when creating, moving, removing, repairing, listing, pruning, or troubleshooting Git worktrees.
GitHub Actions CI/CD best practices for .github/workflows/*.yml, workflow_call, release, deploy, test, build, and pipeline automation. Use when writing, reviewing, or fixing GitHub Actions workflows. Enforce thin workflows: GitHub Actions only orchestrates checkout, setup, auth, cache, artifacts, env, and calls Taskfile tasks; real pipeline logic belongs in Taskfile.yml or specific Taskfile.*.yml files. Load taskfile skill when creating or editing those tasks.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. Trigger on requests like "simplify this code", "clean up", "refactor for clarity", "make this more readable", or after writing significant code that could benefit from refinement.
Build dagger.io-inspired project landing pages and documentation sites using pure CSS (CSS Layers, OKLCH colors, BEM naming). Use when creating marketing websites, project homepages, docs sites, or landing pages that follow the dagger.io aesthetic: warm cream canvas, navy ink, generous whitespace, rounded white cards. Triggers: "landing page", "project site", "docs site", "dagger style", "marketing page", "product page", "harbor satellite site", or building any static site with this visual language. Works with Hugo or standalone HTML. Do NOT use for dashboard/app UI.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Write idiomatic, production-grade Go code following Google's Go Style Guide. Use when writing, reviewing, or refactoring any Go (.go) code including libraries, CLI tools, servers, and tests. Triggers: any Go code generation, "write Go", "Go function", "Go package", "Go test", "refactor Go", "review Go code", "fix Go style", "idiomatic Go", or producing .go files. Do NOT use for non-Go languages.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it under a project-local temp directory such as .opencode/tmp/ when available; otherwise use ~/.agents/tmp/. Read the target file before writing if it already exists.
Suggest the skills to be used, if any, by the next session.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
