shipshitdev/session-documenter
bundles/session/skills/session-documenter/SKILL.md
Session documentation workflow.
$ 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: Jun 4, 2026, 6:47 AM310.2s3 files scanned
SKILL.md
- name:
- session-documenter
- description:
- Session documentation workflow.
- version:
- 1.0.0
- tags:
- session, documentation, workflow, productivity
Session Documenter Skill
Document work, decisions, and context with explicit commands.
Contract
Inputs:
- Current session context
- Files changed, decisions made, blockers, and next steps
- Optional task or PRD references
Outputs:
- Appended session entry in
.agents/SESSIONS/YYYY-MM-DD.md - 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 - You tell me what to track: decisions, files changed, mistakes
/end- I write the full 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
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/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026