skills.rest
xtrm-dev
xtrm-devOFFICIAL
Explore all skills by this author →
GitHub

session-close-report

Generate an end-of-session technical handoff report with cleanup checks and issue tracking.

4|1|Updated Nov 1, 2025
Search Tags:#changelog#documentation#cleanup#orchestration#handoff#session report
One-click install
npx skills add https://github.com/xtrm-dev/specialists --skill session-close-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-close-report
Source: https://github.com/xtrm-dev/specialists/tree/main/.xtrm/skills/default/session-close-report
Command: npx skills add https://github.com/xtrm-dev/specialists --skill session-close-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of ending a working session by turning scattered progress, decisions, and open threads into one reliable handoff artifact for the next agent.

Core Features & Use Cases

  • Session Cleanup: Verifies worktrees, background jobs, processes, and tmux sessions are clean before reporting.
  • Handoff Reporting: Produces or updates the same-day source-of-truth report with summary, issues closed, problems, code changes, and next priorities.
  • Operational Sync: Keeps documentation, changelog entries, memories, and handoff links aligned so follow-up work is easy to resume.
  • Use Case: At the end of a development session, generate a complete report that preserves context, records unresolved blockers, and points the next agent to the most important follow-up tasks.

Quick Start

Use the session-close-report skill to generate and update the end-of-session handoff report for today's work.

Frequently Asked Questions about session-close-report

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

FAQPage Schema
How do I generate an end-of-session technical handoff report for agent orchestration?▼

A session handoff report consolidates scattered progress, decisions, and open threads into one reliable artifact, ensuring the next agent can resume work with full context and actionable next-step priorities.

What is included in a session close report for development workflows?▼

It includes a work summary, issues closed, unresolved problems, code changes, and next priorities, while keeping documentation, changelog entries, and handoff links aligned for easy follow-up work resumption.

How do I verify worktrees and background jobs are clean before ending a session?▼

Run session cleanup checks that inspect active processes, tmux sessions, and worktrees before generating the final handoff report to ensure no lingering background jobs remain.

Can I update the same-day source-of-truth report without losing previous session context?▼

Yes, you can update the same-day source-of-truth report without losing context, because the Skill preserves unresolved blockers and records actionable next-step context for follow-up work.

What is the best way to synchronize changelog entries and memories during session close?▼

Apply operational sync checks that align documentation, memories, and handoff links before reporting to ensure changelog entries and memories are fully synchronized during session close.

Related Skills

Explore More Software Engineering Skills→
ucirelloucirello
2

run-long-running-processes-in-tmux

Manage long-running processes in detached tmux sessions with command injection and output capture.

Community
Intermediate
robertgussrobertguss
103

handoff

Create structured Markdown session handoff documents with decisions and next steps.

Community
Basic
p-o-ke-naep-o-ke-nae

feature-lifecycle

Coordinate end-to-end feature development workflows across GitHub issues and pull requests.

Community
Advanced
product-on-purposeproduct-on-purpose
527

wrap-session

Automate end-of-session documentation and handoff artifacts across project files.

Official
Basic