end-session

Summarize session work, log changes, and update NEXT.md and Linear issues.

6|Updated Apr 8, 2026

Search Tags:#changelog #linear #git-workflow #session-logging #end-session #next.md

Ready to run

npx skills add https://github.com/withpiper/pipekit --skill end-session-withpiper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/withpiper/pipekit/tree/main/skills/end-session
Command: npx skills add https://github.com/withpiper/pipekit --skill end-session-withpiper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session wrap-up is error-prone and time-consuming. This skill automates the closing process by summarizing the session, collecting reflections, and generating a persistent session log that feeds changelogs and NEXT.md updates.

Core Features & Use Cases

Automatically summarize what happened this session and record key decisions.
Log session changes to Strategy/Doc4_Changelog.md as a running record.
Propose a cumulative version bump based on work since the last version.
Capture user reflections and commit a session log for future reference.
Coordinate updates to NEXT.md and related Linear issues as part of the closing flow.

Quick Start

Invoke /end-session on your feature branch after finishing a task to generate a session log and update NEXT.md

Frequently Asked Questions about end-session

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

FAQPage Schema

How do I automate end-of-session wrap-up and generate a session log?▼

To automate end-of-session wrap-up, invoke the end-session command on your feature branch. It enforces preflight checks, summarizes session changes, and generates a persistent session log that feeds into your changelog and NEXT.md updates.

What is the best way to update NEXT.md and Linear issues after finishing a feature task?▼

The best way to update NEXT.md and Linear issues is to run an automated end-of-session wrap-up. It orchestrates updates to related Linear issues and NEXT.md while committing a structured session log for future reference.

How do I log session changes to a changelog file automatically?▼

You can log session changes to a changelog file by running an end-of-session command. It automatically records a running log of session changes to Strategy/Doc4_Changelog.md as part of the closing flow.

Can I compute a version bump based on git workflow changes since the last release?▼

Yes, you can compute a version bump based on recent work. The end-of-session process proposes a cumulative version bump by analyzing the session changes committed on your feature branch.

Does the session logging process require a specific branch or pipeline setup?▼

The session logging process is applied across feature work on a VBW/Linear pipeline. It requires sessions to close on a feature branch where artifacts are committed to logs and NEXT.md.

When should I not use an automated session reflection tool?▼

You should not use an automated session reflection tool if your workflow lacks a feature branch or NEXT.md pipeline. It enforces preflight checks and targets structured VBW/Linear environments, making it unsuitable for unstructured or non-linear git workflows.