session-end

Wraps up Claude Code sessions by logging decisions, capturing learnings, and committing work.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill session-end-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/workflows/session-end
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill session-end-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work done in an AI coding session is easily lost between sessions: decisions go unlogged, learnings are forgotten, changes stay uncommitted, and the next session wastes time re-discovering context. This workflow ensures nothing falls through the cracks when ending a session. ## Core Features & Use Cases - Session Inventory and Commit: Runs git status, diff, and log to summarize uncommitted changes and unpushed commits, then proposes conventional commit messages with user confirmation. - Decision and Learning Capture: Prompts logging of architecture decisions, reusable prompts, and gotchas into decision logs, CLAUDE.md, or memory systems like Animus MCP. - Quality and Metrics Reporting: Optionally audits AI-generated outputs with signal-audit, scrubs published content, and reports drift scores and token spend in a structured SESSION SUMMARY block. - Use Case: After a multi-hour feature implementation, run this workflow to commit changes safely, log three key tradeoff decisions, update TODO.md, and produce a next-session starting point. ## Quick Start Ask Claude to run the session-end workflow to wrap up the current session, commit pending work, and summarize decisions before you stop for the day.

Frequently Asked Questions about session-end

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

FAQPage Schema
How do I wrap up a Claude Code session cleanly?▼

Run the session-end workflow before closing. It inventories uncommitted changes via git status, prompts you to log decisions and learnings, suggests conventional commit messages, and produces a structured summary with next-session starting points.

How to capture architecture decisions from a coding session?▼

The workflow reviews the session for high-leverage decisions such as technology choices, scope changes, and tradeoffs, then prompts you to log each with a one-line summary and rationale via a decision-log skill if available.

Does session-end push commits to remote automatically?▼

No. The workflow never pushes without explicit user approval and never commits files that might contain secrets like .env or credentials. It reports unpushed commit counts and asks before any push, respecting code freezes.

When should I not use a session wrap-up workflow?▼

Skip it when the session was purely exploratory with no code changes, when everything is already committed and pushed, or when you prefer to handle wrap-up manually. It is designed for sessions with meaningful work.

Can session-end track token spend and output quality?▼

Yes, optionally. If ai-spend is installed it reports estimated token costs, and if signal-audit is available it scores AI-generated outputs over 200 words, flagging anything below 6/10 for human review.