shipshitdev/session-end
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.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library session-endInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 14, 2026, 4:48 AM113.4s2 files scanned
SKILL.md
- name:
- session-end
- description:
- >-
- version:
- 1.0.0
- tags:
- session, workflow, documentation, productivity
Session End
Document your session before clearing context. This is a TWO-STEP process: /session-end documents, then user manually runs /clear.
Contract
Inputs:
- Redacted session context and changed-file summary
- Pending tasks, blockers, decisions, and reusable rules/workflows
Outputs:
- Saved session documentation with secrets removed
- Clear next-step instruction for context reset
Creates/Modifies:
.agents/sessions/YYYY-MM-DD.md- Related
.agents/task or summary files when delegated tosession-documenter
External Side Effects:
- None
Confirmation Required:
- Before rewriting existing session entries
- Before promoting captured rules or skills outside session docs
Delegates To:
session-documenterrules-capturefor unresolved reusable preferencesskill-capturefor reusable workflows that should become skills
Workflow
Step 1: Document Session
When invoked, immediately:
- Run the
session-documenterskill to save a redacted session summary - Let it complete — it will document tasks, decisions, files changed, patterns, and mistakes without storing secrets
- Confirm documentation saved
Cross-platform note: If your agent platform doesn't support skill invocation, follow the session-documenter workflow manually by reading the
session-documenterskill definition.
Step 2: Remind User to Clear
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.
Important Notes
- ONE FILE PER DAY: Session documenter appends to the same day's file
- Multiple invocations: Each one adds a new session entry
- Does NOT clear context: User must run
/clearmanually after - Redaction is mandatory: Do not store API keys, tokens, passwords, cookies,
private credentials, or secret values from the conversation. Replace them with
[REDACTED_SECRET]and summarize the surrounding context.
Related Skills
- session-start — Loads preferences and today's session after clearing
- session-documenter — The underlying documentation skill
Related Skills
shipshitdev/typescript-refactor
development
VerifiedTrustedCommunity
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/typescript-expert
tools
VerifiedTrustedCommunity
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/turborepo
tools
VerifiedTrustedCommunity
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/tailwind
tools
VerifiedTrustedCommunity
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
30SKILL.mdUpdated Jul 14, 2026