write_session_report
Document coding sessions by creating structured reports with accomplishments, changes, and next steps for organized project tracking in Obsidian.
Instructions
Write a session report to the Obsidian vault. Use this at the end of coding sessions, after completing significant tasks, or when wrapping up work phases. The report will be saved with proper frontmatter and timestamps.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Short title for the session (e.g., 'Refactored auth module') | |
| summary | Yes | Brief summary of what was accomplished | |
| details | No | Detailed description of changes, decisions, and context | |
| files_changed | No | List of files that were modified | |
| next_steps | No | List of follow-up tasks or TODOs | |
| tags | No | Tags for categorization (e.g., ['refactoring', 'auth', 'security']) | |
| project | No | Project name for organization | |
| folder | No | Subfolder within Claude-Sessions (default: uses project name or root) |