end-session

Reconcile session outcomes across repositories, GitHub Issues, memory, and workspace cleanup.

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill end-session-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/end-session
Command: npx skills add https://github.com/jwh3times/holland-vip --skill end-session-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work sessions leave residue scattered across git branches, uncommitted edits, GitHub Issues, and conversation context that disappears when the session ends. This Skill closes out a session by routing every outcome to its proper home so nothing learned is lost. ## Core Features & Use Cases - Session stock-take: Reconstructs what happened using git status, logs, and PR listings, then tags each item with a destination such as public repo, private repo, issue, memory, or drop. - Memory and repository reconciliation: Writes durable facts to project memory files, routes private decisions and research into the nested private repository, and reports publish state without unauthorized pushes. - Issue tracker updates: Comments on, closes, or creates GitHub Issues in the correct public or private tracker, files human follow-up actions with wiki runbooks, and cleans up the local workspace with dry-run-first deletion. - Use Case: After a day of feature work on a Next.js portfolio site, run the skill to record decisions, update open Issues, verify branch states, and produce a summary naming what the next session should pick up first. ## Quick Start Ask the assistant to end the session and reconcile today's work across both repositories, Issues, and memory.

Frequently Asked Questions about end-session

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

FAQPage Schema
How do I close out a coding session without losing context?▼

Take stock of the session with git status, logs, and open PRs, then tag each outcome with a destination such as the repository, an Issue, project memory, or deletion. The skill walks this process and produces a summary naming what the next session should pick up first.

How do I update GitHub Issues at the end of a work session?▼

List open issues in each tracker with gh issue list, then comment progress on existing issues, close landed work with a comment naming the PR, and create new issues for discoveries. The skill lists all intended writes for user approval before executing them.

Can this skill commit or push my private repository automatically?▼

No. The skill reviews private edits with git diff and status, reports ahead counts relative to upstream, and names uncommitted or unpushed work, but it never commits or pushes the private repository without explicit user authorization.

Why is git clean -fdx dangerous in a repo with a nested private repository?▼

git clean -fdx deletes all gitignored content, including node_modules and the entire gitignored private/ directory containing the companion repository. The skill only uses the -nd dry-run form for inspection and deletes confirmed paths with explicit rm commands.

What is the difference between end-session and a handoff document?▼

End-session records durable outcomes, updates trackers, and cleans the workspace, while a handoff document captures the conversation's reasoning for the next session. When the next session needs the reasoning rather than the outcomes, the skill points to the handoff flow instead.