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/weekly-review
development
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Aug 31, 2026