session-summary

Appends per-session entries to a feature's session-log.md for clean handoffs.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill session-summary-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/swingerman/engineer/tree/main/engineer/skills/session-summary
Command: npx skills add https://github.com/swingerman/engineer --skill session-summary-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session on a DAE feature ends, context about what was done, what is in progress, and what comes next is lost. This Skill writes a structured, human-readable session entry so the next session picks up cleanly without re-reading machine handoffs. ## Core Features & Use Cases - Session log entries: Appends a structured entry (previous tasks, current task, next tasks, open questions) to features/NNN-<slug>/session-log.md, never overwriting prior entries. - Session-end infrastructure teardown: Runs dae_infra.py teardown to shut down session-scoped infrastructure while leaving long-running emulators untouched, recording the result in the log. - Merged-branch detection: Checks whether the current branch is merged into main and defers cleanup to the post-merge skill based on the configured autonomy level. - Use Case: At the end of a day working on a feature branch, invoke it to log what was completed, what is mid-flight, and the concrete next tasks, so tomorrow's session starts from the log instead of memory. ## Quick Start Ask the agent to wrap up the session and write the session log entry for the current feature branch.

Frequently Asked Questions about session-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a session log for a feature branch?▼

Invoke the session-summary skill at the end of your work session. It resolves the current feature from the branch, synthesizes handoffs and git activity, and appends a structured entry with completed, current, and next tasks to session-log.md.

What is the difference between session-log.md, handoffs, and progress.md?▼

They serve three readers: handoffs are machine-readable per-invocation records, progress.md is a glanceable machine-derived tracker, and session-log.md is a human-readable per-session narrative. They do not duplicate each other.

When should session-summary not be used?▼

Do not use it mid-session, for syncing the tracker (use progress-log), or for per-skill records. It runs once per session end, since multiple entries per day would make the log unreadable.

Does session-summary shut down running emulators at session end?▼

By default no. The teardown step leaves entries configured with teardown: leave-running untouched, since emulators are expensive to restart. Only entries marked teardown: session-end or always are shut down.

What happens if my branch is already merged when the session ends?▼

The skill checks whether the branch is an ancestor of origin's default branch. If merged, it defers cleanup to the post-merge skill, auto-invoking it at medium or high autonomy and surfacing the finding at low autonomy.