close-session

Detects open loops, runs safe cleanup, and preserves session knowledge at work-session close.

Updated May 8, 2026
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill close-session-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-session
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/close-session
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill close-session-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a work session often leaves dangling threads: unmerged PRs, live scheduled triggers, open tasks, uncommitted work, and knowledge that dies with the session. This Skill closes a session systematically so nothing dangles and nothing risky happens silently. ## Core Features & Use Cases - Open-loop scan: Silently inventories unmerged PRs, uncommitted work, live triggers and probes, webhook subscriptions, open tasks, and uncaptured knowledge. - Safe/risky split: Auto-runs reversible cleanup (cancel own probes, merge verified green PRs, mark done tasks) and pauses for approval on anything irreversible or outward-facing. - Typed knowledge preservation: Routes durable learnings into a 3-tier brain architecture (boot docs, domain skills, queries/git) by decay rate, with propose-only handling for authority docs. - Use Case: At the end of a long coding session, say "close session" and receive a closure report listing what was auto-resolved, what awaits your approval, what was deferred, and what knowledge was committed. ## Quick Start Tell the assistant to close out the current session and tie off all loose ends before you stop working.

Frequently Asked Questions about close-session

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

FAQPage Schema
How do I close out a Claude Code session cleanly?▼

Invoke the close-session skill by saying "close session" or "wrap up". It scans for open loops, auto-runs safe reversible cleanup, pauses for approval on risky items, preserves knowledge by type, and delivers a closure report.

What does the session closure scan check?▼

The scan checks unmerged PRs with their check status, uncommitted work via git status, live scheduled triggers and self-probes, active PR webhook subscriptions, open tasks, and uncaptured durable knowledge from the session.

Will it merge pull requests automatically at session close?▼

It merges a PR automatically only when all required checks are green and the change is verified with real evidence. PRs with failing required checks or unverified high-blast-radius changes are surfaced for explicit approval instead.

Can it delete scheduled triggers when closing a session?▼

It cancels only triggers provably created by the current session as self-probes. Recurring operational triggers, other sessions' check-ins, or any trigger of ambiguous ownership are left untouched and reported.

Where does session knowledge get saved?▼

Knowledge is routed by decay rate into a 3-tier system: domain skill SKILL.md files for domain depth, registries like gap_registry.md and lessons_learned.md for findings, and propose-only patches for authority docs like CLAUDE.md.

When should I not use the close-session skill?▼

Do not use it for closing a single PR or issue, for release or deployment go-no-go gates, or for start-of-day briefings. It is specifically for ending an entire working session.