my-session-wrap

Summarize Git changes, update documentation, and record learnings at session end.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill my-session-wrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-session-wrap
Source: https://github.com/Kwondongkyun/claude-code-settings/tree/main/skills/my-session-wrap
Command: npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill my-session-wrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

코딩 세션이 끝날 때 변경 내용을 자동으로 요약하고 문서를 업데이트하며 학습 기록을 남김으로써 수고를 덜고, 팀 공유를 용이하게 한다.

Core Features & Use Cases

  • 변경 내용 요약: git diff와 git status를 분석해 변경 파일 목록과 차이를 명확히 제시
  • 문서 업데이트 자동화: 관련 문서를 필요한 위치에 자동으로 업데이트
  • 학습 기록 기록: 오늘 배운 점과 해결한 문제를 간단히 정리
  • Use Case: 긴 개발 세션 종료 시 리포트를 1페이지로 생성해 팀에 공유

Quick Start

세션 종료 시 변경 요약과 문서 업데이트를 즉시 실행한다.

Frequently Asked Questions about my-session-wrap

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

FAQPage Schema
How do I automate git change summarization and documentation updates when a coding session ends?

Automating session wrap-up involves analyzing git diff and git status to summarize changed files, updating related documentation automatically, and recording learnings to streamline development workflow reporting.

What is the best way to generate an end-of-session development report for team sharing?

Generating an end-of-session report requires consolidating Git changes, documentation updates, and learning notes into a structured one-page summary, ensuring clear communication of development session progress.

Can I automatically record learning notes and solved problems from my development workflow?

Automatically recording learning notes captures the problems solved and insights gained during a development session, structuring them into a concise summary for future reference and team knowledge sharing.

How does multi-agent analysis work for git diff summarization and doc updates?

Multi-agent git diff summarization uses a deterministic 4-agent Phase 1 for parallel analyses, followed by Phase 2 validation, producing a consolidated results report that details changes and documentation updates.

Do I need external dependencies to automate session wrap-up and change detection?

Automating session wrap-up requires no external dependencies, operating independently to detect Git changes, update documentation, and compile learning notes through its internal multi-agent workflow architecture.

When should I not use automated session wrap-up for my development workflow?

Automated session wrap-up is not ideal for highly granular or continuous integration workflows requiring real-time updates, as it is specifically designed for structured end-of-session reporting rather than incremental tracking.