session-log
/session-log
At the end of a work session, record decisions, learnings, measurable impact and next steps in the project's docs and, if configured, the user's Obsidian vault. Use when the user says "wrap up", "log this session" or runs /alexis:session-log.
- Author
- diegoaguilar2209 ↗
- Repository
- alexis ↗
- Licence
- MIT
- Last repository change
- 30.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
At the end of a work session, record decisions, learnings, measurable impact and next steps in the project's docs and, if configured, the user's Obsidian vault. Use when the user says "wrap up", "log this session" or runs /alexis:session-log.
Triggers from the description
Original author description
At the end of a work session, record decisions, learnings, measurable impact and next steps in the project's docs and, if configured, the user's Obsidian vault. Use when the user says "wrap up", "log this session" or runs /alexis:session-log.
How it works
- What to record
- Where
- Rules
SKILL.md preview
---
name: session-log
description: At the end of a work session, record decisions, learnings, measurable impact and next steps in the project's docs and, if configured, the user's Obsidian vault. Use when the user says "wrap up", "log this session" or runs /alexis:session-log.
disable-model-invocation: true
model: haiku
effort: low
---
# Session log
Keeps the project's memory in files the user controls, so the next session starts with context, and builds session by session the evidence of impact (what matters in a performance review, a pitch or a CV). Reply in the user's language.
## What to record
Review the session and write ONLY what changes the project's future:
- Decisions and their reason (one line each).
- Reusable learnings (a bug and its root cause, a pattern that worked).
- Status: what is done, what is half-done.
- Next 3 steps.
- Impact, only if there was a measurable result: what changed, how much (number and unit), for whom and how it was measured. If there is no number yet, note which metric would prove it.
## Where
1. `docs/decisions.md` in the project: new entry at the top with the date (`## YYYY-MM-DD`).
2. `docs/impact.md` in the project: one row per measurable result (date, result, metric, evidence).
3. If the user's `~/.claude/CLAUDE.md` defines `ALEXIS_VAULT`:
- Note in `<vault>/1-Projects/<project-name>.md` (status, decisions, `[[links]]`).
- If there was impact, one line in `<vault>/2-Areas/Career/Impact.md` with date, result and number.
4. If a learning applies to every project, propose (do not apply) a change to the user's CLAUDE.md or suggest `/alexis:improve`.
## Rules
- Work and client projects: in a personal vault only the result in general terms ("cut campaign cost 18%"), never data, table names, client names or credentials.
- Short sentences; do not narrate what was done step by step.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · diegoaguilar2209/alexis | 90 | MIT |
| jl-cmd-projects/claude-dev-env | 100 | MIT |
| yg-codes/srepowers | 100 | MIT |
| filip-podstavec/claude-leverage | 90 | MIT |
| felpix-studios/social-science-research | 90 | MIT |
Database snapshot: 13.11.2026 · package version 897e447288a1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95obsidian-tracker-session-log
Log current session to Obsidian project. Use when the user invokes /session-log. - 100session-save
Save current session context and work summary to the Obsidian vault when the user asks to record or save their work. Automatically generates a structured markdown document capturing what was discussed, decisions made, and next steps. Triggers: 기록해, 저장해, save session, 세션 저장, 작업… - 100log
Save learnings, decisions and mistakes from the current conversation to the personal learning log right now, without waiting for the session to end. Use when the user runs /learning-log:log or says "log this", "save this learning", "add this to my log". - 100learn
Capture session learnings and decisions to .suiperpower/learnings.md. Use when the user wants to save what they learned, log decisions, or wrap up a session. - 100session-close
End a session under token/iteration limits: write handoff, session log, memory, and teach notes as markdown into the Obsidian personal vault Work/{project}/. Use when session ends, budget hit, user says handoff/close session, or rem-ralph finishes. - 100save-session-log
Write a structured Markdown record of the current session — the requests, the analyses run, the files touched, decisions made, and open next steps — to the project's session-logs dir (one dated file per invocation), then propagate any durable result/decision into the wiki…