bundles/session/skills/session-end/SKILL.md
Save session wrap-up documentation before clearing context by running the session-documenter workflow and writing `.agents/sessions/YYYY-MM-DD.md`. Use when ending a session, preparing to run `/clear`, or asked to document what changed before context is reset.
npx skillsauth add shipshitdev/library session-endInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Document your session before clearing context. This is a TWO-STEP process: /session-end documents, then user manually runs /clear.
Inputs:
Outputs:
Creates/Modifies:
.agents/sessions/YYYY-MM-DD.md.agents/ task or summary files when delegated to session-documenterExternal Side Effects:
Confirmation Required:
Delegates To:
session-documenterrules-capture for unresolved reusable preferencesskill-capture for reusable workflows that should become skillsWhen invoked, immediately:
session-documenter skill to save a redacted session summaryCross-platform note: If your agent platform doesn't support skill invocation, follow the session-documenter workflow manually by reading the
session-documenterskill definition.
After documentation is complete, tell the user:
Session documented to .agents/sessions/YYYY-MM-DD.md
NEXT STEP: Run /clear to clear the conversation context.
Your session is safely preserved and will be loaded on next /session-start.
/clear manually after[REDACTED_SECRET] and summarize the surrounding context.development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.