session-end

Featured

Use when the user asks to end, wrap up, clear, hand off, or prepare continuity for a Codex/AgentDeck session. Summarizes current work, captures next-step memory, updates durable project notes only when needed, and writes a concise handoff for the next session.

AI & Automation 247 stars 52 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
80
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Session End Use this skill at the end of a work session, before `/clear`, `/new`, switching tasks, or handing work to another Codex/Claude session. ## Purpose Produce a concise handoff that lets the next session continue without rereading the whole transcript. Separate temporary handoff notes from durable project knowledge. ## Workflow 1. Read `CLAUDE.md` and the top of `DEVELOPMENT_LOG.md` (a generated aggregate — the entries behind it live in `docs/devlog/entries/`). 2. Inspect the current work state: ```bash git status --short git diff --stat ``` 3. If files changed, inspect only relevant diffs needed to summarize the work. Do not revert unrelated changes. 4. Summarize: - goal and current outcome - files changed and why - verification run and results - unresolved risks or blockers - exact next action for the next session 5. Update durable docs only when warranted: - Development log: for meaningful fixes, architectural decisions, hardware findings, or known pitfalls, create `docs/devlog/entries/YYYY-MM-DD-<slug>.md` (first line `# YYYY-MM-DD — title`, sections as `###`, links relative to the repo root), then run `pnpm devlog:build`. When committing is within the task scope, include the entry and its regenerated aggregates together. Never edit `DEVELOPMENT_LOG.md` or `docs/devlog/YYYY-MM.md` by hand. - `CLAUDE.md`: update only for project-wide architecture, invariants, setup, or workflow changes. - `AGENTS.md`: update only for persistent agen...

Details

Author
puritysb
Repository
puritysb/AgentDeck
Created
7 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

session-end

MUST use when user says 'bye', 'goodbye', 'good night', 'gnight', 'done for today', 'that's all', 'that's it', 'see you', 'see ya', 'let's stop', 'stopping here', 'wrapping up', 'signing off', 'closing down', 'done', 'finished for now', 'talk later', 'cya'. The user does NOT use slash commands — detect these natural session-ending phrases and run the full wrap-up automatically.

0 Updated today
lethilu4796
AI & Automation Solid

session-end

MUST use when user says 'bye', 'goodbye', 'good night', 'gnight', 'done for today', 'that's all', 'that's it', 'see you', 'see ya', 'let's stop', 'stopping here', 'wrapping up', 'signing off', 'closing down', 'done', 'finished for now', 'talk later', 'cya'. The user does NOT use slash commands; detect these natural session-ending phrases and run the full wrap-up automatically.

71 Updated today
faizkhairi
AI & Automation Listed

finished

End-of-session closure for a research or code repository. Records what actually changed into the project's own handoff and log files, distinguishing verified work from work merely attempted, and reports what was left uncommitted. Use when wrapping up a work session so the next one can resume without re-deriving state. Its start-of-session twin is sitrep.

58 Updated 3 days ago
scdenney