Generate an Obsidian session report at the end of a coding session. Summarizes commits, tests, decisions, blockers, and next steps. Triggers on: end session, session report, wrap up, done for today.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add igorilic/agentic-orchestration --skill session-report --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Session Report?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/igorilic-session-report)More formats (shields.io, HTML) on the badges page.
---
name: session-report
description: >
Generate an Obsidian session report at the end of a coding session.
Summarizes commits, tests, decisions, blockers, and next steps.
Triggers on: end session, session report, wrap up, done for today.
---
## Session Report Generator
### Step 1: Gather Context
```bash
git diff --stat HEAD~10 2>/dev/null || git diff --stat
git log --oneline --since="4 hours ago" 2>/dev/null || git log --oneline -10
git branch --show-current
```
### Step 2: Generate Report
Create markdown with frontmatter (date, project, branch, tags) and sections:
- **Summary**: 2-3 sentences of what was accomplished
- **Work Done**: Commit-by-commit summary
- **Tests**: Count added/modified, pass/fail status
- **Decisions Made**: Any architectural choices (link ADRs)
- **Blockers / Open Questions**: Unresolved items
- **Next Steps**: Checklist for next session
- **References**: Ticket IDs, PR links, ADR links
### Step 3: Save
Save to: `~/Obsidian/Dev/Sessions/<YYYY-MM-DD>-<project>-session.md`
If Obsidian MCP is available, use it. Otherwise write directly.
### Step 4: Update Sprint
Update `docs/context/CURRENT_SPRINT.md` with current status.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".