From session-closer
Summarizes what changed during a session, writes a session document, and handles smart committing. Triggers on 'close session', 'save session', 'end of session', 'wrap up session', 'summarize session', 'what did we do', 'session summary'.
npx claudepluginhub bartekck/bartek-marketplace --plugin session-closerThis skill uses the workspace's default tool permissions.
Analyze what changed during the session, write a session summary document to `./docs/sessions/`, and help commit properly.
Guides end-of-session context persistence by silently analyzing git diffs, logs, status, and conversation to propose learnings, decisions, conventions, and tasks for ctx add.
Generates markdown diary entries for coding sessions, capturing accomplishments, files changed, git commits, decisions, next steps, and handoffs. Triggers on 'save diary', 'log session', or 'wrapping up'.
Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.
Share bugs, ideas, or general feedback.
Analyze what changed during the session, write a session summary document to ./docs/sessions/, and help commit properly.
Run all steps below.
Skip Step 1 — the agent has already gathered context and will provide it. Steps 2-3 still apply.
Gather context about what happened this session:
git diff --stat — uncommitted changesgit diff --stat --cached — staged changesCombine into a session picture. The conversation context is the primary source — git fills in details.
If the user says "you already know" or similar, synthesize entirely from conversation context and git.
Scan ./docs/sessions/ for existing session files.
001NNN in filenames, use NNN + 1Session files follow the pattern: session_NNN_short_description.md
Derive the short description (2-4 words, snake_case) from the session's main focus.
Create ./docs/sessions/session_NNN_description.md:
# Session NNN — YYYY-MM-DD — Short Title
## Summary
Detailed implementation-level summary of what was done. Describes features
added, bugs fixed, refactors applied — at the feature/change level, not
file-level or commit-level. Multiple paragraphs if the session was substantial.
## Decisions
- **[Choice]**: [reasoning]
# Session 003 — 2026-03-29 — Auth System Setup
## Summary
Implemented JWT-based authentication with refresh token rotation. Added
login and register endpoints to the API. Set up middleware that validates
tokens on protected routes and returns 401 with clear error messages.
Integrated bcrypt for password hashing with configurable salt rounds.
Updated the user model to include refresh token storage and expiration
tracking.
## Decisions
- **JWT over session cookies**: API-first architecture, need stateless auth for mobile clients
- **Refresh token rotation**: Single-use refresh tokens limit damage from token theft
# Session 004 — 2026-03-29 — Dashboard UI
## Summary
Built the main dashboard page with a stats grid showing active users,
revenue, and error rate. Added a recent activity feed that live-updates
via SSE. Implemented responsive layout that collapses the sidebar on
mobile. Connected all components to the existing API endpoints.
Use the conventional-commits skill for commit message format reference.
If git diff --stat and git diff --stat --cached show nothing: offer to commit only the session document.
docs: add session NNN summary — <short description>
Analyze the diff to determine if changes span multiple concerns:
Single concern — draft one conventional commit message:
git add -A or git add .)Multiple concerns — suggest splitting:
If committing with code changes: Include the session file in the same commit. The commit message covers the code work; the session file is just another file in the changeset.
If committing separately (user preference or no code changes):
docs: add session NNN summary — <short description>
Use conventional-commits skill for format reference. Stage only the session file. Commit after user approval.