Streamlines session wrap-up by automating documentation, analysis, and cleanup tasks.

Install

mkdir -p .claude/skills/session-wrap && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6710" && unzip -o skill.zip -d .claude/skills/session-wrap && rm skill.zip

Installs to .claude/skills/session-wrap

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
219 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Check git status
  • Extract key learnings
  • Suggest follow-up tasks
  • Automate documentation updates

How it works

Runs multiple analysis agents in parallel to validate changes, extract lessons, and format documentation.

Inputs & outputs

You give it
Session summary and file change list
You get back
Documentation updates and summary report

When to use session-wrap

  • Documenting work before committing
  • Cleaning up project context at the end of a shift
  • Extracting actionable learnings from a task
  • Preparing summaries for PR descriptions

About this skill

Session Wrap Skill

Comprehensive session wrap-up workflow with multi-agent analysis.

Execution Flow

┌─────────────────────────────────────────────────────┐
│  1. Check Git Status                                │
├─────────────────────────────────────────────────────┤
│  2. Phase 1: 4 Analysis Agents (Parallel)           │
│     ┌─────────────────┬─────────────────┐           │
│     │  doc-updater    │  automation-    │           │
│     │  (docs update)  │  scout          │           │
│     ├─────────────────┼─────────────────┤           │
│     │  learning-      │  followup-      │           │
│     │  extractor      │  suggester      │           │
│     └─────────────────┴─────────────────┘           │
├─────────────────────────────────────────────────────┤
│  3. Phase 2: Validation Agent (Sequential)          │
│     ┌───────────────────────────────────┐           │
│     │       duplicate-checker           │           │
│     │  (Validate Phase 1 proposals)     │           │
│     └───────────────────────────────────┘           │
├─────────────────────────────────────────────────────┤
│  4. Integrate Results & AskUserQuestion             │
├─────────────────────────────────────────────────────┤
│  5. Execute Selected Actions                        │
└─────────────────────────────────────────────────────┘

Step 1: Check Git Status

git status --short
git diff --stat HEAD~3 2>/dev/null || git diff --stat

Step 2: Phase 1 - Analysis Agents (Parallel)

Execute 4 agents in parallel (single message with 4 Task calls).

Session Summary (Provide to all agents)

Session Summary:
- Work: [Main tasks performed in session]
- Files: [Created/modified files]
- Decisions: [Key decisions made]

Parallel Execution

Task(
    subagent_type="doc-updater",
    description="Document update analysis",
    prompt="[Session Summary]\n\nAnalyze if CLAUDE.md, context.md need updates."
)

Task(
    subagent_type="automation-scout",
    description="Automation pattern analysis",
    prompt="[Session Summary]\n\nAnalyze repetitive patterns or automation opportunities."
)

Task(
    subagent_type="learning-extractor",
    description="Learning points extraction",
    prompt="[Session Summary]\n\nExtract learnings, mistakes, and new discoveries."
)

Task(
    subagent_type="followup-suggester",
    description="Follow-up task suggestions",
    prompt="[Session Summary]\n\nSuggest incomplete tasks and next session priorities."
)

Agent Roles

AgentRoleOutput
doc-updaterAnalyze CLAUDE.md/context.md updatesSpecific content to add
automation-scoutDetect automation patternsskill/command/agent suggestions
learning-extractorExtract learning pointsTIL format summary
followup-suggesterSuggest follow-up tasksPrioritized task list

Step 3: Phase 2 - Validation Agent (Sequential)

Run after Phase 1 completes (dependency on Phase 1 results).

Task(
    subagent_type="duplicate-checker",
    description="Phase 1 proposal validation",
    prompt="""
Validate Phase 1 analysis results.

## doc-updater proposals:
[doc-updater results]

## automation-scout proposals:
[automation-scout results]

Check if proposals duplicate existing docs/automation:
1. Complete duplicate: Recommend skip
2. Partial duplicate: Suggest merge approach
3. No duplicate: Approve for addition
"""
)

Step 4: Integrate Results

## Wrap Analysis Results

### Documentation Updates
[doc-updater summary]
- Duplicate check: [duplicate-checker feedback]

### Automation Suggestions
[automation-scout summary]
- Duplicate check: [duplicate-checker feedback]

### Learning Points
[learning-extractor summary]

### Follow-up Tasks
[followup-suggester summary]

Step 5: Action Selection

AskUserQuestion(
    questions=[{
        "question": "Which actions would you like to perform?",
        "header": "Wrap Options",
        "multiSelect": true,
        "options": [
            {"label": "Create commit (Recommended)", "description": "Commit changes"},
            {"label": "Update CLAUDE.md", "description": "Document new knowledge/workflows"},
            {"label": "Create automation", "description": "Generate skill/command/agent"},
            {"label": "Skip", "description": "End without action"}
        ]
    }]
)

Step 6: Execute Selected Actions

Execute only the actions selected by user.


Quick Reference

When to Use

  • End of significant work session
  • Before switching to different project
  • After completing a feature or fixing a bug

When to Skip

  • Very short session with trivial changes
  • Only reading/exploring code
  • Quick one-off question answered

Arguments

  • Empty: Proceed interactively (full workflow)
  • Message provided: Use as commit message and commit directly

Additional Resources

See references/multi-agent-patterns.md for detailed orchestration patterns.

When not to use it

  • If the session was purely read-only
  • When no changes have been made

Prerequisites

git

Limitations

  • Requires context of changes to be accurate
  • Parallel execution can be resource heavy

How it compares

It synthesizes multi-perspective analysis into structured documentation instead of raw chat logs.

Compared to similar skills

session-wrap side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
session-wrap (this skill)17moReviewIntermediate
task-handoff-checklist01moReviewIntermediate
workthrough108moReviewBeginner
doc-check42moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by team-attention

View all by team-attention

gmail

team-attention

This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail. Supports multi-account Gmail integration for reading, searching, sending, and label management.

169

agent-council

team-attention

Collect and synthesize opinions from multiple AI agents. Use when users say "summon the council", "ask other AIs", or want multiple AI perspectives on a question.

29

session-analyzer

team-attention

This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.

24

youtube-digest

team-attention

This skill should be used when the user asks to "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈", or provides a YouTube URL for analysis. Extracts transcript, generates summary/insights/Korean translation, and tests comprehension with 9 quiz questions across 3 difficulty levels. Optional Deep Research for web-based follow-up.

23

dev-scan

team-attention

개발 커뮤니티에서 기술 주제에 대한 다양한 의견 수집. "개발자 반응", "커뮤니티 의견", "developer reactions" 요청에 사용. Reddit, HN, Dev.to, Lobsters 등 종합.

10

google-calendar

team-attention

Google 캘린더 일정 조회/생성/수정/삭제. "오늘 일정", "이번 주 일정", "미팅 추가해줘" 요청에 사용. 여러 계정(work, personal) 통합 조회 지원.

11

You might also like

task-handoff-checklist

inernoro

开发任务完成后自动扫描变更,从导航、文档、规则、工作流、测试、风险、代码质量、后续事项八个维度生成结构化交接报告,让验收者零追问即可核对。触发词:"交接"、"验收"、"handoff"、"/handoff"。

00

workthrough

bear2u

Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.

1085

doc-check

coder

Checks if code changes require documentation updates

427

pr-draft-summary

openai

Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.

326

create-pr-description

antinomyhq

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.

213

github-contributor

daymade

Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.

17

Search skills

Search the agent skills registry