| name | log-session |
| description | This skill should be used when the user says "log session", "save this session", "end of session", or wants to record what was learned and built during the current coding session. Appends a new dated entry to SESSIONS.md. |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Edit, Glob |
Log Session
Append a new learning session entry to SESSIONS.md at the root of the current project directory.
Steps
- Read
SESSIONS.md to understand existing format and avoid duplicating the most recent session date
- Review the current conversation to extract what was concretely worked on: bugs fixed, features implemented, concepts encountered, files changed
- Read
KNOWLEDGE.md — note any concepts marked ⚠️ or ❌ that genuinely appeared in this session
- Append a new session entry following the template in references/sessions-template.md
Rules
- Use today's actual date in
YYYY-MM-DD format. If an entry for today already exists, append a new one as YYYY-MM-DD (2), YYYY-MM-DD (3), etc.
- "What was built" entries must be specific — mention function names, file paths, Rust concepts (e.g. "fixed lifetime issue in
parse_articles_dir()" not "fixed a bug")
- Minimum 5 questions per difficulty level
- Questions must be grounded in what was actually worked on — no generic Rust trivia
- Do not repeat questions that appear in previous sessions
- Easy: recall or one-liner answers
- Medium: requires reasoning, edge cases, or connecting two concepts
- Hard: architecture, tradeoffs, ownership/type system depth, or "what would break if..."
- Leave the "My answers" section blank for the user to fill in
- For each ⚠️ or ❌ concept from
KNOWLEDGE.md that came up in this session, include at least one question per difficulty level targeting that specific gap — tie it to something concrete from the session, not abstract trivia. Do not include knowledge-reinforcing questions for concepts that didn't surface.
