From bns-dev
Create a structured summary of the current conversation and save it to sessions/
How this command is triggered — by the user, by Claude, or both
Slash command
/bns-dev:session-summaryThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Session Summary Create a structured summary of the current conversation. ## Process 1. **Create sessions directory** if it doesn't exist: 2. **Analyze the conversation** to identify: - Main objective/question - Approaches tried (successes and failures) - Final solution or answer - Key discoveries along the way - Lessons for similar future situations 3. **Generate a descriptive slug** from the main topic (kebab-case, 3-5 words) 4. **Write the summary** to `sessions/YYYY-MM-DD_<slug>.md` 5. **Confirm** the file location to the user ## Output Format ## Naming Co...
Create a structured summary of the current conversation.
Create sessions directory if it doesn't exist:
mkdir -p sessions
Analyze the conversation to identify:
Generate a descriptive slug from the main topic (kebab-case, 3-5 words)
Write the summary to sessions/YYYY-MM-DD_<slug>.md
Confirm the file location to the user
# <Title>
**Date:** YYYY-MM-DD
**Objective:** What we were trying to accomplish
---
## Summary
Brief description of outcome
## The Journey
### What Didn't Work
- Failed attempts and why they failed
### What Worked
- The successful approach
## The Solution
### Key Findings
Details of what was discovered/solved
### Code/Queries (if applicable)
Working examples
### Key Insights
Important takeaways
## Lessons Learned
What to remember for next time
## Related Resources
- Links, tables, files discovered
File: YYYY-MM-DD_<slug>.md
Examples:
2026-01-05_sms-segmentation-query-search.md2026-01-05_warehouse-cost-analysis.md2026-01-05_dbt-model-debugging.mdnpx claudepluginhub chekos/bns-marketplace --plugin bns-dev/wrapSummarize the entire current conversation and persist it so future sessions can recover context.
/sessionlogCaptures current session context as structured markdown log with key decisions, commands, problems, resolutions, and files changed. Saves to ./SessionLogs/session-DDMMYY-HH:MM.md
/diaryCreates a structured markdown diary entry from the current Claude Code session transcript, covering conversation, tools used, files edited, errors, and decisions.