Session Wrap

Use when the user wants to wrap up the current coding session, summarize the current session before ending work, document learnings, decide what to commit, or says 总结会话, 会话总结, 收尾, 会话收尾, 结束会话, 总结本次会话.

9 stars 1 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add leonsong09/session-wrap --skill session-wrap

Manual install

git clone --depth 1 https://github.com/leonsong09/session-wrap.git /tmp/session-wrap
mkdir -p ~/.claude/skills
cp -r /tmp/session-wrap/. ~/.claude/skills/session-wrap

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Session Wrap Skill

## Overview

Use this skill to close out the **current** coding session in a way that is easy to resume later. Focus on what was actually finished, what is still open, what was learned, and what should happen next.

## Core Rules

- Scope is the **current session** unless the user explicitly asks for a broader range.
- Prioritize outcomes, decisions, learnings, and follow-up actions over process chatter.
- Do not output a chronological 流水账.
- Do not claim work is completed unless there is evidence in the session, git status, or validation output.
- If the user asks to write files, commit, or update docs, summarize first and then confirm the action.

## Workflow

### Step 1: Confirm scope

Default to the current session. If the user already gave a clear wrap-up request, do not ask extra questions.

Clarify only when needed:
- current session only or also include earlier sessions
- whether to include commit advice
- whether to produce a handoff note or just a chat summary

### Step 2: Inspect the working tree

Collect the minimum evidence needed to summarize the session accurately.

Recommended commands:

```bash
git status --short
git diff --stat
git log --oneline -n 10
```

If the repository state is not available, say so explicitly and continue with the session evidence you do have.

### Step 3: Summarize completed work

Summarize by **workstream** instead of by timestamp.

Preferred structure:
- 本次完成
- 关键决策
- 涉及文件 / 模块
- 已做验证

Read the full skill on GitHub

Details

Skill name: session-wrap
Repository: leonsong09/session-wrap
License: MIT
Repo updated: 30 March 2026

FAQ

What does the Session Wrap skill do?

How do I install the Session Wrap skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add leonsong09/session-wrap --skill session-wrap. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Session Wrap popular?

It lives in leonsong09/session-wrap, which has 9 GitHub stars and 1 forks.

Related skills

Thermo Nuclear Code Quality Review

Oreo992/thermo-nuclear-code-quality-review

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

Software Development

Project Daily Summary

leonsong09/project-daily-summary

Use when the user wants a same-day Codex work summary grouped by project folder or repository, combining today's Codex sessions, extracted plans, completed items, commits, and uncommitted changes, or says 项目日报, 日报, 今日工作总结, 按项目总结今天, 总结今天所有 Codex 会话, 总结今天会话+提交+未提交改动.

Software Development

Ask Codex

bookSiYi1412/ask-codex

TRIGGER when: user requests implementation work, repo exploration, data/log inspection, broad codebase search, impact analysis, verification-heavy shell work, or explicitly mentions Codex ("用 codex 做", "让 codex 执行", "ask codex to...", "use codex", "delegate to codex"). Also trigger for heavy internal subtasks that Claude Code might otherwise offload to a lightweight model/Haiku. DO NOT TRIGGER when the task is primarily user-facing product judgment, architecture choice, git/PR/release operations, or requires multi-turn clarification before useful work can begin. This skill routes work between

Software Development

Product Requirements Review

fourierwang66666/product-requirements-review

Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common se

Software Development

Codewiki

ekuttan/codewiki

Generate a structured product knowledge base from codebase scanning. Creates a codewiki/ folder with architecture docs, user flows, API reference, service maps, and more. Also generates CLAUDE.md. Handles single repos, monorepos, and multi-repo microservices. Use when asked to document a project, generate a knowledge base, map architecture, create onboarding docs, or set up CLAUDE.md for a codebase.

Software Development

Isms P Audit

basejb/isms-p-audit-skill

ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.