菜单
Protocol for cleanly ending a work session including filing issues, running quality gates, updating status, committing, and handing off context. Use when wrapping up a coding session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | session-completion |
| description | Protocol for cleanly ending a work session including filing issues, running quality gates, updating status, committing, and handing off context. Use when wrapping up a coding session. |
When ending a work session, complete these steps to ensure clean handoff and no lost context.
Create issues for anything that needs follow-up:
Run the project's quality checks:
mix test, zig build test, npm test, etc.)git add <specific files>
git commit -m "message"
If using an issue tracker that stores files in the repo (e.g., Beads), sync those changes too.
Provide context for the next session:
git push automatically - the user will push manuallygit commit automatically - only commit when the user explicitly asksSession ending. Here's the status:
1. Completed:
- [What was finished]
2. In Progress:
- [What's partially done, with context]
3. Issues Filed:
- [New issues created for follow-up]
4. Next Steps:
- [What to focus on next session]
Clean session completion ensures:
Core Elixir language guidelines covering common pitfalls like list access, immutability, module organization, struct access, date/time handling, and OTP patterns. Use when writing or reviewing Elixir code.
Ecto best practices covering preloading, schema types, changeset validation, field access, security, and migration conventions. Use when working with Ecto schemas, changesets, queries, or migrations.
Best practices for testing Elixir applications with Ecto.SQL.Sandbox, including background process handling, Oban testing, and test output quality. Use when writing or reviewing Elixir tests.
Phoenix HEEx template rules covering interpolation syntax, form building, class lists, conditional rendering, comments, and common anti-patterns. Use when writing or reviewing HEEx templates.
Phoenix LiveView patterns covering streams, JavaScript interop (hooks, colocated scripts, push events), testing, and form handling. Use when building or reviewing LiveView features.
Phoenix 1.8 framework conventions covering layouts, routing, components, icons, forms, HTTP clients, and design file handling. Use when building or reviewing Phoenix web applications.