菜单
Save the current Codex session's work summary before ending a conversation. Use when the user says /wrap, wrap, 세션 정리, 세션 저장, 작업 내용 저장, 메모리 저장, 세션 마무리, 오늘 여기까지, or asks to preserve progress for the next Codex session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | wrap |
| description | Save the current Codex session's work summary before ending a conversation. Use when the user says /wrap, wrap, 세션 정리, 세션 저장, 작업 내용 저장, 메모리 저장, 세션 마무리, 오늘 여기까지, or asks to preserve progress for the next Codex session. |
Persist a concise summary of the current session so the next Codex conversation can resume with less rediscovery. This complements automatic Codex session history; it records intent, decisions, verification, and follow-up work in project-readable files.
Prefer project-local storage when the current directory is a repository:
.codex/session-notes/session-YYYY-MM-DD-topic.md
Also append a short entry to OMX notepad when .omx/ exists or the project already uses OMX:
.omx/notepad.md
If neither project-local target is available, save under:
~/.codex/memories/session-YYYY-MM-DD-topic.md
git status --short --untracked-files=all when inside a git repository---
name: YYYY-MM-DD topic session summary
description: One-line summary of the saved context
type: codex-session
---
## Session Summary (YYYY-MM-DD)
### Completed
- item
### In Progress
- item
### Decisions
- decision — Why: reason
### Verification
- command/result or "Not run — reason"
### Risks / Blockers
- item
### Next Steps
- [ ] item
Append a brief entry rather than duplicating the full note:
## YYYY-MM-DD — topic
- Saved: `.codex/session-notes/session-YYYY-MM-DD-topic.md`
- Summary: one sentence
- Next: one or two follow-up bullets
Report:
Saved:
- path
Summary:
- completed: N
- in progress: N
- next steps: N
코드 분석/탐색 시 토큰을 최소화하면서 정확도를 최대화하는 도구 선택과 검색 전략. ast-grep(sg) 구문 인식 검색, ripgrep, fd, LSP, Glob의 우선순위·조합 가이드. 코드 검색, 심볼 탐색, 리팩토링, 패턴 찾기, "어디서 쓰이는지", "구현체 찾아줘" 등의 요청 시 자동 적용. 출처: msbaek/dotfiles `<tool_preferences>` 패턴을 로컬 환경에 어댑테이션.
Upgrade all development tools via Homebrew, sync Brewfile packages, and verify RTK hooks. Use this skill whenever the user mentions daily upgrade, brew update, package upgrade, claude-code update, 데일리 업그레이드, 브루 업데이트, 패키지 업데이트, 일일 업그레이드, or any request to bring their dev environment up to date — even casual mentions like 'update everything' or '오늘 업데이트 좀'.
Use when the user asks to brainstorm, design before coding, refine requirements, or turn an idea into an approved spec before implementation. This skill explores intent, compares approaches, presents a design, writes a spec to `docs/specs/.local/`, and blocks code changes until the design is approved.
Analyze the current changes and conversation context, generate an intent-focused Git commit message, and run `git commit`. Use when the user asks to commit changes or wants commit automation around `git commit`, `commit`, `--amend`, `--push`, or `--no-verify`. The skill instructions are in English, but the generated commit message itself must be written in Korean.
Copy only the meaningful, paste-ready artifact from the current task to the clipboard, usually code, SQL, JSON, shell commands, or a clean text snippet without surrounding explanation. Use when the user asks to put something on the clipboard, copy only the useful part, copy just the query/code, remove commentary, or prepare a clean paste-ready result from recent work.
Clean Codex crew state. Use when the user says /crew-cleanup, crew-cleanup, crew 정리, or asks to remove old .codex/crew seed/run/cycle files.