shipshitdev/session-documenter
bundles/session/skills/session-documenter/SKILL.md
Documents work, decisions, and context from the current session by writing structured entries to `.agents/sessions/YYYY-MM-DD.md`. Triggers on `/start`, `/end`, "document this session", "save session notes", or automatically at session wrap-up to capture decisions, files changed, mistakes, and next steps.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library session-documenterInstall 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 1, 2026, 5:17 AM97.3s3 files scanned
SKILL.md
- name:
- session-documenter
- description:
- >-
- version:
- 1.0.0
- tags:
- session, documentation, workflow, productivity
Session Documenter Skill
Document work, decisions, and context.
Contract
Inputs:
- Current session context, redacted for secret-like values
- Files changed, decisions made, blockers, and next steps
- Optional task or PRD references
Outputs:
- Appended session entry in
.agents/sessions/YYYY-MM-DD.mdwith secrets removed - Related summary/task updates when needed
Creates/Modifies:
.agents/sessions/daily session file.agents/memory/*.mdwhen a decision changes durable project context (architecture, deployment, migrations, gotchas)
External Side Effects:
- None
Confirmation Required:
- Before rewriting existing session history
- Before promoting session notes into permanent rules or skills
Delegates To:
rules-capturefor reusable preferences discovered during the sessionskill-capturefor reusable workflows discovered during the sessionsession-endfor wrap-up flow
Commands
| Command | Action |
|---------|--------|
| /start | Begin new session - creates/appends to today's file, loads context |
| /end | Finalize session - writes entry with all tracked work, updates related files |
How It Works
/start- Creates.agents/sessions/YYYY-MM-DD.mdif missing, or loads existing context- During session - Track decisions, files changed, mistakes
/end- Write a redacted session entry with flowcharts, decisions, next steps
Critical Rules
Session File Naming (ONE FILE PER DAY)
✅ CORRECT: .agents/sessions/2025-11-15.md
❌ WRONG: .agents/sessions/2025-11-15-feature-name.md
Multiple sessions same day → Same file, Session 1, Session 2, etc.
Flowcharts (MANDATORY for features)
Include flowchart for:
- New features
- Feature modifications
- Multi-component bug fixes
Redaction (MANDATORY)
Before writing session notes:
- Replace API keys, tokens, passwords, cookies, private credentials, and secret
values with
[REDACTED_SECRET]. - Summarize sensitive command output instead of copying it verbatim.
- Do not store full request/response payloads if they contain personal data, private URLs, or credentials; record only the decision-relevant fields.
Session Entry Structure
- Session number and title
- System flow diagram (mermaid or text)
- Affected components (frontend, backend, data, external)
- What was done (task checklist)
- Key decisions (with rationale)
- Files changed
- Mistakes and fixes
- Next steps
Related Files to Update
.agents/memory/*.md— when a decision changes durable repo context (architecture, deployment, migrations, gotchas). Bump the file'slast_verifieddate when you touch it.
References
- Full guide: Phases, automation, validation, examples
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