sl

Session Logs (/sl) - Session Continuity Command

Load and summarize recent Live Session Logs (LSL) to provide continuity from previous work sessions.

Instructions

Goal: Load recent LSL files and produce a summary to establish context continuity.

Tooling Rules (read first — these keep /sl prompt-free)

Use exactly the two ls forms below for discovery, and Read for content. Nothing else.

Do NOT use Glob. Claude Code no longer exposes a Glob tool to the main agent — search is done through Bash. An earlier version of this skill mandated Glob and banned Bash outright, which made every /sl run open with an apology about the preferred tool being unavailable before falling back to an ad-hoc find. The two commands below are the replacement; they are pre-allowed, so they do not prompt.

The two allowed discovery commands (<ROOT> is .specstory/history for the current project, or the absolute coding path for Step 3):

ls -d <ROOT>/[0-9][0-9][0-9][0-9]/[0-9][0-9]      # list YYYY/MM tranche dirs, oldest→newest
ls -1r <ROOT>/<YYYY>/<MM>                          # list one month's files, NEWEST FIRST

Both are matched by user-level allow rules (see Permissions), so they run prompt-free in any project.

Two things the numeric [0-9] pattern buys you — do not "simplify" it away:

• .specstory/history also contains non-LSL subtrees (logs/, docs/). A recursive **/*.md sweep over the coding project returns ~23,000 files, almost all noise. The numeric year/month pattern selects only real LSL tranches.
• Listing one month at a time keeps the result at tens of files, not thousands.

Never reach for these — each one triggers a prompt even where a matching Bash(...) allow rule exists, because the permission matcher cannot statically resolve the command it runs:

• find … -exec <cmd> (the -exec payload is opaque to the matcher)
• xargs <cmd> / `cmd` / $(cmd) (nested command)
• pipelines (ls … | head, find … | sort) — every stage needs its own allow rule, and the project-scoped ones only exist in coding