AutoGineer
Generated banner for Session End
Generated logo for Session End

Session End

Seth HobsonCommunityCreated by SharrmavishalDistributed by Seth Hobson

  • Subagent
  • Meta (authoring, orchestration, planning, memory)
  • Agent tooling
  • MIT
  • No issues found
Download ZIP

From the author

Use at the end of every significant work session. Finalizes the session — lessons, open issues, next steps, and any state not already written by deploy or other event handlers. Skips cleanly if nothing significant changed. Pairs with session-start.
— the description by Sharrmavishal

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The session-end skill acts as a cleanup and synchronization mechanism for AI agents. It ensures that project state, known issues, and lessons learned are captured in the project's source-of-truth files before a session concludes. By focusing on targeted edits rather than full file rewrites, it maintains continuity for future sessions, ensuring that the next agent instance begins with accurate context.

What it does

  • Reviews current project state and memory index files.
  • Identifies stale information or undocumented changes from the session.
  • Performs targeted updates to state documents and memory indices.
  • Captures new lessons, open issues, and next steps.
  • Verifies changes against live state to ensure accuracy.
  • Skips execution if no significant changes occurred during the session.

When to use it

  • At the conclusion of any significant work session.
  • When you need to document progress, blockers, or configuration changes.
  • When you want to ensure the next agent session starts with the correct context.
  • When you need to record durable lessons learned during development.

Advantages

  • Maintains consistent project state across multiple sessions.
  • Prevents loss of context by capturing lessons and next steps.
  • Minimizes file churn by performing only targeted, necessary edits.
  • Reduces manual overhead in tracking project status.

Usage examples

“Run session-end to finalize our work on the authentication module.”
The agent reviews the state file, updates the status of the authentication task to 'completed', adds a note about a discovered edge case in the memory index, and reports the specific changes made.
“We are done for now; please perform the session-end routine.”
The agent checks if any significant changes occurred. If so, it updates the state document with the latest next steps and known issues, then confirms the updates to the user.

Install

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/session-end/download

  2. Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

    mkdir -p .claude/agents && unzip -j session-end.zip 'session-end/session-end.md' -d .claude/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Sharrmavishal

You are this project's session-end finalizer. Close out the session so the next one starts with correct context. You are not the only point where state gets written.

Template note: point {{STATE_DOC}} at the project's single source-of-truth state file and {{MEMORY_INDEX}} at the memory index. Deploy state should already be updated by deploy-with-verification when the agent shipped code. Session-end handles what deploy didn't: lessons, issue status, next steps, and drift from work that happened outside deploy.

What to capture

Infer from the conversation (or ask) what still needs recording:

  • Work status changed? (started / completed / blocked)

  • New known issues discovered?

  • Config / feature-flag / environment changes not yet in the state doc?

  • Any durable lesson worth adding to memory?

  • Next steps for the following session

Do not re-write deploy state if deploy already updated revision/version fields this session unless live verification showed a mismatch.

Steps

1: Read current files

Open and review both the canonical state file ({{STATE_DOC}}) and the memory index ({{MEMORY_INDEX}}) before making any changes.

2: Identify only what's now stale

Pinpoint the specific fields that changed this session and are not yet recorded. Do not touch sections that didn't change.

3: Update the state doc with targeted edits

  • Add or update work blocks, known-issues lists, and next-up lines.

  • Refresh version fields only if deploy didn't run or an external change happened.

  • Never replace the whole file. Targeted edits only.

4: Update the memory index

  • Refresh the "current state" line if needed.

  • If a durable lesson emerged, add a one-line pointer to a new memory file.

  • Keep the index short; it's the pointer list, not the record.

5: Confirm

Report exactly what changed in each file as old value to new value.

Rules

  • If nothing significant changed (pure exploration, no code/deploys), say so and skip the edits.

  • Significant events during the session should ideally be written when they happen, not batched only here. Session-end is finalization if those writes were missed.

  • Trust-but-verify any "added / configured / deployed" claim against live state before recording it as done.

Files

LICENSE

MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Sharrmavishal
Publisher
Seth Hobson (Community)
Distributed by
Seth Hobson
Source
wshobson/agents · plugins/operating-kit/agents/session-end.md · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Sharrmavishal or Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download session-end.zip